search for: sp_namp

...9 01:04:18 2007 *************** *** 66,71 **** --- 66,72 ---- if (spw->sp_expire == -1) { debug3("account expiration disabled"); + #ifndef __QNXNTO__ } else if (daysleft < 0) { logit("Account %.100s has expired", spw->sp_namp); return 1; *************** *** 75,80 **** --- 76,82 ---- "Your account will expire in %d day%s.\n", daysleft, daysleft == 1 ? "" : "s"); buffer_append(&loginmsg, buf, strlen(buf)); + #endi...

I encountered a couple of strange events with respect to password authentication this morning. Two of our staff were unable to login onto several systems using their usual passwords. Both users had last logged in on these hosts using their accounts and passwords on Friday past. The two accounts could not log on to any of the servers for which they had access and the message log on each showed

maybe this is a silly question ;-) But why is it possible to login on a machine with a locked account (passwd -l ) via pubkey-authentication (authorized_keys) ? I use OpenSSH3.01p1on Solaris8 with PAM support so I thought this should not happen. If this is the normal behaviour and built in intentionally what would be the easiest way to lock an account without deleting the users authorized_keys ?