2 ms·
Not at all. The problem was that the crypto for the same library on two different OSes was implemented differently, which lead to an error encrypting on Linux a
by HWR_14 3y ago
Not at all. The problem was that the crypto for the same library on two different OSes was implemented differently, which lead to an error encrypting on Linux and decrypting on Solaris. Ironically, this would have been avoided if they had rolled their own.
It is an instance of "make sure you have backups when deploying to production"
- devit 3y agoNot the crypto, but rather the getpass() function, which simply reads a password from standard input without echoing it. Since the function uses a static buffer, there is a limit on the password length, which apparently on Solaris was set to the absurdly low value of 8 (glibc uses a more reasonable value: 8192).
- HWR_14 3y agoThanks for the correction. I assumed getpass() did some crypto work in addition to just getting raw keyboard input.