Probably because it isn't officially sanctioned, which apparently was the reason the more common libcs never added support for bcrypt directly. - "The securit

Probably because it isn't officially sanctioned, which apparently was the reason the more common libcs never added support for bcrypt directly. - "The security departments of some customers look at recommendations they get and evaluate the deployed systems based on this. In a few places this led to the problem that the NIST warns people indiscriminately about the use of MD5..." (Note, this was from 2007 when md5 would be in roughly the same state that sha1 is now in.) http://www.akkadia.org/drepper/sha-crypt.html http://www.akkadia.org/drepper/sha-crypt.html https://access.redhat.com/articles/1519843#ok-ok-but-why-not-bcrypt-5 https://access.redhat.com/articles/1519843#ok-ok-but-why-not...