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: Openssh, operator controlled authorized_keys |
|---|---|
| Date: | Wed, 8 Mar 2006 07:37:53 -0800 |
Use the AuthorizedKeysFile directive in sshd_config to point to a file only you have access to, outside the user's home directory. However, this won't allow you to use a single file, unless you want all users to have access to everyone's accounts. Off the top of my head, I can't think of a way to do it with a single file. -----Original Message----- How do I configure openssh so that it'll permit a public key for a user, without giving the user the oppertunity to change/add public keys to the authorized list? Also, is there a way to have a single file with the authorized keys for *all* users? Like /etc/shadow, but for public keys rather than passwrods.
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Openssh, operator controlled authorized_keys, Tan Dang |
|---|---|
| Next by Date: | OpenSSH Centralized Key Server, jvitale |
| Previous by Thread: | Re: Openssh, operator controlled authorized_keys, Tan Dang |
| Next by Thread: | OpenSSH Centralized Key Server, jvitale |
| Indexes: | [Date] [Thread] [Top] [All Lists] |