> OK; markm said it was a crypt() problem (that he caused & fixed); I'm
> not going to belabor that.  (I will, however, express appreciation for
> Mark "taking the heat":  thanks, Mark!)


> But on the point of folks being unable to login, I'm not seeing the
> failure here.

You'll only see it if you have the bad version of crypt-md5.c(1.9)
and you actually use md5 passwords (the salt begins with $1$ when
you look in /etc/master.passwd). The breakage time was less than
24 hours.

o       Mark Murray
O.\_    Warning: this .sig is umop ap!sdn

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to