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: | Openssh, operator controlled authorized_keys |
|---|---|
| Date: | Tue, 7 Mar 2006 16:48:03 -0800 |
I want to control access to my machines via public keys. I'm implanting the private key in a smartcard-like token, and giving the tokens to people for access. They'll use the tokens like smartcards, and ssh-agent can use those RSA keys on the tokens. However, I don't want people to authorize other public keys (ie, not on physical tokens) after they've logged in. 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. Thanks. Steve
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: CVS repos., ilaiy |
|---|---|
| Next by Date: | Re: Openssh, operator controlled authorized_keys, Tan Dang |
| Previous by Thread: | CVS repos., Lawrence Bowie |
| Next by Thread: | Re: Openssh, operator controlled authorized_keys, Tan Dang |
| Indexes: | [Date] [Thread] [Top] [All Lists] |