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: Problem with AllowUsers?

Subject: Re: Problem with AllowUsers?
Date: Thu, 09 Dec 2004 10:02:04 -0800
AllowUsers esw, sidekick

As you can see, the other user has my public key also.  So, for the time 
being, I have a backdoor.

Now, why can't I get in as myself, esw?

You can't separate users with comma, only spaces.

I would also recommend to use the AllowGroups instead, and create a 
"ssh"-group so you add users to the group.

*AllowUsers*
This keyword can be followed by a list of user name patterns, separated 
by spaces. If specified, login is allowed only for
user names that match one of the patterns.  '*' and '?' can be used as 
wildcards in the patterns.  Only user names are valid;
a numerical user ID is not recognized.  By default, login is allowed for 
all users.  If the pattern takes the form USER@HOST
then USER and HOST are separately checked, restricting logins to 
particular users from particular hosts.

Thanks!  I removed the comma and restarted sshd.  I was able to get in.

I didn't even think there was a problem with the format of the
AllowUsers line, so I didn't think to look in the man pages.

I have also taken your suggestion and moved from AllowUsers to
AllowGroups.  The AllowGroups works also.

Thanks!
eric
-- 
  Eric Wagar
  eric@deadhookers.org

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