3 ms·
glibc crypt() uses sha512, IIRC (the thing that encrypts passwords in /etc/shadow). Iterated a number of times to make it suitably expensive. So perhaps not as
by jabl 9y ago
glibc crypt() uses sha512, IIRC (the thing that encrypts passwords in /etc/shadow). Iterated a number of times to make it suitably expensive.
So perhaps not as good has the bespoke password hashing functions, but not a disaster waiting to happen either.
- JoshTriplett 9y agoSalting and iterating would make it more reasonable, but the article (a "best practices" document) didn't say to do that, or why.
- deleted 9y ago[deleted]