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. |

| Subject: | RE: PAM and SSH |
|---|---|
| Date: | Sat, 18 Mar 2006 13:17:19 -0500 |
It does not seem to work. It appears that for sshd, sshusers would have to be their primary group and it is not. It also appears that the Allow* directives act like seives. You have to pass all of the specified criteria to get in. This means they would have be in the right group AND local rather than OR which is what I need. Does anyone know how to do this with PAM? I now have the "remoteusers" group setup so that might make it easier. Ron -----Original Message----- From: Darren Tucker [mailto:dtucker@zip.com.au] Sent: March 16, 2006 4:04 PM To: Ron Wheeler Cc: secureshell@securityfocus.com; rwheeler@artifact-software.com Subject: Re: PAM and SSH Ron Wheeler wrote:
I would like to allow ssh access from 1) anyone on the 192.168.1.0/24 network or 2) anyone on a list of users.
An alternative to using pam_listfile (assuming you're using OpenSSH):
Put your chosen few users into a group, say, "sshusers" then put the
following in sshd_config:
AllowGroups sshusers
AllowUsers *@192.168.1.*
--
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> |
|---|---|---|
| ||
| Previous by Date: | Re: Openssh v4.2-3 vs. HP-UX 11iv1 TCB, Darren Tucker |
|---|---|
| Next by Date: | Re: updating expired passwords following ssh login, user advisory, samuel gipe |
| Previous by Thread: | Re: PAM and SSH (add new options?), Ron Wheeler |
| Next by Thread: | Re: PAM and SSH, Darren Tucker |
| Indexes: | [Date] [Thread] [Top] [All Lists] |