We have one test that tries to handle the case where decrypting a stored password fails because of a changed SECRET_KEY that continues to fail intermittently depending on the random IV that's chosen. One thing that's contributing to this is that the test password is extremely short, increasing the likelihood that decrypting with an incorrect key will return printable garbage instead of unprintable garbage. This change makes the test password string much longer, in hopes that we'll hit failures less frequently. Testing Done: Ran affected unit test.