On Tue, Jul 2, 2013 at 12:52 PM, Alexandre Oliva aol...@redhat.com wrote:
At this point, I'd rather we took the opportunity to fix code that makes
unsafe assumptions about the behavior of crypt than push the problem on
for users to figure out when a glibc upgrade causes passwords to fail to
be
On Jul 1, 2013, Thorsten Glaser t...@mirbsd.de wrote:
This would always avoid returning a NULL value, thus unbreaking
all applications that use that assumption.
It seems to me that this would turn a very visible fault into a silent
fault. In general, the former is more desirable; consider
2 matches
Mail list logo
