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: Locking down ssh config in large env |
|---|---|
| Date: | Tue, 21 Sep 2004 11:08:45 -0700 |
Actually if the .ssh directory is owned by root (and everything in it) with the user not having write access to it, the user cannot delete the .ssh directory. Directories cannot be deleted unless they are empty. You cannot delete a file unless you can write to the directory. This is implemented in the filesystem driver to keep filesystem consistancy. On Sun, 19 Sep 2004 19:14:12 +0900, Derek Martin <code@pizzashack.org> wrote:
This is not sufficient. If the user has write permission to their .ssh directory, they can delete the files in it, and then replace them with their own. If the user has write access to their home directory, the same applies to the entire .ssh directory.
--
END OF LINE
-MCP
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: OpenSSH -- a way to block recurrent login failures?, Warner, Randy |
|---|---|
| Next by Date: | RE: Multiple modes? throught one connection, Tim Nelson |
| Previous by Thread: | Re: Locking down ssh config in large env, Derek Martin |
| Next by Thread: | Re: Locking down ssh config in large env, Derek Martin |
| Indexes: | [Date] [Thread] [Top] [All Lists] |