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: AllowUsers issue

Subject: Re: AllowUsers issue
Date: Fri, 20 Jan 2006 18:01:19 +0200
On 1/20/06, Vladimir Levijev <vladimir.levijev@gmail.com> wrote:

Hi,

You forgot to mention the DenyUsers part:

DenyUsers '*'
AllowUsers myuser

I think you'll find that'll stop any users matching the DenyUsers pattern
(ie all of them).

You only need AllowUsers; if set then users not matching it (or
AllowGroups) will be denied.

Why don't you try, before you "think". Or at least, read the fine
manual. Here is a hint:

man sshd_config | grep Users -A9

Sorry, my bad. It appeared, that parameter takes values without the
quotes. So it acts really strange way if you add '*' (quoted) value.
When I tested what I've proposed (I've tested it with unprivileged
user and root, adding unprivileged user to AllowUsers) I could not
login with root any longer (usually I can) but could with the user. So
it looked like it works. Now I figured if I add * (unquoted) value to
DenyUsers it denies all. And the option AllowUsers works fine (accept
only listed) alone.

My apologies,

--
[vl@dimir]#

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