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]

RE: SCO OpenServer 5.0.5 authenticates locked accounts

Subject: RE: SCO OpenServer 5.0.5 authenticates locked accounts
Date: Tue, 18 Apr 2006 10:29:07 -0400
Thanks for the recommendation. Unfortunately it did not work. I also
tried rebuilding configure with autoconf after adding the
AC_DEFINE(LOCKED_PASSWD_STRING, "*LK*") to the *-*-sco3.2v5* definitions
and then re-ran configure and re-compiled. I'm still getting the same
results (authenticating to a locked account using password
authentication, not public/private key).

-----Original Message-----
From: Darren Tucker [mailto:dtucker@zip.com.au] 
Sent: Monday, April 17, 2006 10:21 AM
To: Powell, Scott
Cc: secureshell@securityfocus.com
Subject: Re: SCO OpenServer 5.0.5 authenticates locked accounts

Powell, Scott wrote:
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.

Unless you also rebuild configure with "autoconf" or "autoreconf" and 
reran configure then your changes would not have taken effect.

Does anyone have any recommendations or workarounds?

Try adding:

#define LOCKED_PASSWD_STRING "*LK*"

to defines.h and recompiling.

-- 
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4  37C9 C982 80C7 8FF4 FA69
     Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.


<Prev in Thread] Current Thread [Next in Thread>