As detailed here, the default SecureRandom provider for Linux systems can be very slow (15 minutes for 15 characters on my system, possibly depending on user keyboard/mouse input, and with no progress indicator whatsoever). This did not make the bot unresponsive, but strongly delays its generation of a random key. The previous link to an SO post suggests using the SHA1PRNG algorithm, which is a lot faster (near instantaneous). This PR uses the SHA1PRNG algorithm, which is common in desktop Java implementations, and bumps up the key length to 80 characters, to (although somewhat poorly) compensate for SHA1PRNG's less secure nature.
Type of change
[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation (adds or revises project documentation)
Changelist
Type of change
Local configuration: