kernel-packages team mailing list archive

[Dan Quade <1349252@xxxxxxxxxxxxxxxxxx>]

Alright, sorry for my rudeness and impatience. Granted, I am not
familiar with how these things are usually handled around here. I am
aware this is mainly an upstream issue, but from crypt(3)'s man page I
assumed distros are the ones who choose whether to implement Blowfish
support.

To quote the man page:  Blowfish (not in mainline glibc; added in some
Linux distributions)

A good example is FreeRADIUS which has support for crypt(3) but no
native bcrypt support. On distributions where crypt(3) supports
blowfish, freeradius will be able to use it as well through
crypt_blowfish.

Another problem si that PHP not only supports blowfish, but makes it the
default cypher. Obviously not Ubuntu's problem, but apparently they
think blowfish is better than SHA-x. In my opinion if there is no
consensus, then a reasonable compromise would be to try and support both
cyphers wherever possible.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1349252

Title:
  crypt(3) lacks Blowfish support

Status in “glibc” package in Ubuntu:
  Won't Fix
Status in “linux” package in Ubuntu:
  Invalid

Bug description:
  crypt(3) bundled with Ubuntu's GNU C Library supports MD5, DES, SHA256
  and SHA512 hashing methods, but lacks support for Blowfish (aka
  bcrypt).

  There is a patch available from Openwall:
  http://www.openwall.com/crypt/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1349252/+subscriptions