On Thu, Jun 27, 2013 at 12:28:22AM +, 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
Debian Bug Tracking System dixit:
If you wish to submit further information on this problem, please
send it to 714...@bugs.debian.org.
Oh well, a '%' is not in the list of DES inputs, so differing
is permitted, but returning NULL is so very not nice.
Shortening the string shows “DES” can be
On Wed, Jun 26, 2013 at 10:48:55PM +, Thorsten Glaser wrote:
Debian Bug Tracking System dixit:
If you wish to submit further information on this problem, please
send it to 714...@bugs.debian.org.
Oh well, a '%' is not in the list of DES inputs, so differing
is permitted, but returning
Aurelien Jarno dixit:
As the function is POSIX compliant, it looks like to me a documentation
issue. Should this bug be reassigned to manpages-dev to mention the fact
that the function might return NULL in case of error?
The NULL-in-case-of-error mentioned by POSIX is when the
function is not
On Wed, Jun 26, 2013 at 11:53:39PM +, Thorsten Glaser wrote:
Aurelien Jarno dixit:
As the function is POSIX compliant, it looks like to me a documentation
issue. Should this bug be reassigned to manpages-dev to mention the fact
that the function might return NULL in case of error?
The
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*
On Thu, Jun 27, 2013 at 12:28:22AM +, 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
Aurelien Jarno dixit:
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.
It's freaking late at night, and I just spent hours fighting
with gnulib and *then* hours I'd
8 matches
Mail list logo
