Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Secure-Shell
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

RE: SCO OpenServer 5.0.5 authenticates locked accounts

from [Michael P. Brininstool] Network Security [Permanent Link]
Subject: RE: SCO OpenServer 5.0.5 authenticates locked accounts
Date: Mon, 17 Apr 2006 09:00:16 -0600 
I noticed this 9 years ago on Solaris.  My work-around to this day is to
'chmod 000 ~lockeduser/.ssh'  This is easily reversible, just as the *LK*
can be removed from the encrypted string.  I noticed this problem only when
the user is using key instead of password authentication.

--
Michael P. Brininstool

-----Original Message-----
From: Powell, Scott [mailto:SPowell@verisign.com] 
Sent: Thursday, April 13, 2006 4:08 PM
To: secureshell@securityfocus.com
Subject: SCO OpenServer 5.0.5 authenticates locked accounts

I have noticed that SSH compiled for SCO OpenServer 5.0.5 is authenticating
locked accounts. I have tried re-compiling the latest portable version,
4.3p2, as well as some older versions. I also tried a Skunkware version
supplied by SCO. All of these are authenticating locked accounts. I even
messed around in configure.ac and added AC_DEFINE(LOCKED_PASSWD_STRING,
"*LK*") to the *-*-sco3.2v5* definitions (locked accounts have a *LK* in the
shadow file as a prefix to the encrypted password hash.

Does anyone have any recommendations or workarounds?

Thanks,
Scott
[More messages with this same subject...]




<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  openssh: Limiting bandwidth on ssh (stdin-to-dd), Mark Holden
Next by Date:  Re: openssh: Limiting bandwidth on ssh (stdin-to-dd), Robert J. Stull
Previous by Thread:  Re: SCO OpenServer 5.0.5 authenticates locked accounts, Darren Tucker
Next by Thread:  Re: SCO OpenServer 5.0.5 authenticates locked accounts, Venkatachalam, Saravanakumar
Indexes:  [Date] [Thread] [Top] [All Lists]