This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: #714219 - libc6: crypt(3) returns NULLâ told you so
- From: Thorsten Glaser <t dot glaser at tarent dot de>
- To: Carlos O'Donell <carlos at redhat dot com>
- Cc: 714219 at bugs dot debian dot org, Alexandre Oliva <aoliva at redhat dot com>, libc-alpha at sourceware dot org
- Date: Fri, 19 Jul 2013 09:22:45 +0200 (CEST)
- Subject: Re: #714219 - libc6: crypt(3) returns NULLâ told you so
- References: <alpine dot DEB dot 2 dot 10 dot 1307181210350 dot 25054 at tglase dot lan dot tarent dot de> <51E86A9D dot 9080800 at redhat dot com>
On Thu, 18 Jul 2013, Carlos O'Donell wrote:
> > * CVE-2013-4122: Handle NULL returns from glibc 2.17+ crypt()
> > (Closes: #716835)
> I'm happy to see applications being fixed to follow the
> documented standard.
Which is a violation of historic practice and âcommon lawâ.
Iâd be as happy to see the documented standard fixed.
Oh well. I uploaded a new cvs package to Debian sid
yesterday that handles NULL returns as well (review
of that diff is welcome, ofc), but IMHO the greater
issue remains.
bye,
//mirabilos
--
ÂMyISAM tables -will- get corrupted eventually. This is a fact of life. Â
âmysql is about as much database as ms accessâ â âMSSQL at least descends
from a databaseâ âit's a rebranded SyBaseâ âMySQL however was born from a
flatfile and went downhill from thereâ â âat least jetDB doesnât claim to
be a databaseâ (#nosec) âââ Please let MySQL and MariaDB finally die!