On Thu, Jun 27, 2013 at 12:28:22AM +0000, Thorsten Glaser wrote: > Aurelien Jarno dixit: > > >ambiguity that crypt can return NULL for any failure (i.e. not > >successful completion): > > Indeed, but, one, it doesn’t list any other error code (nor do > the glibc manpages) and two, there _is_ something called common > law: it’s been like this for decades. > > >This is *your* interpretation of POSIX. Quoting it, there is no > > Do you, by inaction, want to sign responsible for all security > holes introduced into previously-working code in the archive > that now, without even a recompilation, breaks? > > Or will you add some small patch fixing this behaviour and > feed that patch also upstream? >
Please provide a patch, and I will add it in the next upload. If you don't, you will sign responsible for all security holes introduced into previously-working code in the archive. -- Aurelien Jarno GPG: 1024D/F1BCDB73 aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
