>> The only way I can think of is to pre-create an .ssh directory, and
>>chown
>> it to root with no write permissions.
>And, also create a root owned file (any name; empty is fine)
>within that directory. Then, the user can not remove the
>directory---it has contents that the user can not remove.
>>Doesn't work; since the user has rwx permission in their home
>>directory,
>>they can just delete anything below it.
>Not quite, see above.
The user can still RENAME the .ssh directory, whether or not a file
owned by root is inside of it.
---Aaron
- Re: Restricting RSA Authentication. dreamwvr
- Re: Restricting RSA Authentication. Kevin Sullivan
- Re: Restricting RSA Authentication. David Pick
- Re: Restricting RSA Authentication. Carlos Carvalho
- Re: Restricting RSA Authentication. Shiloh Costa
- Re: Restricting RSA Authentication. Dan Astoorian
- Re: Restricting RSA Authentication. Greg A. Woods
- Re: Restricting RSA Authentication. Randolph J. Herber
- Re: Restricting RSA Authentication. dreamwvr
- Re: Restricting RSA Authentication. Randolph J. Herber
- Re: Restricting RSA Authentication. - Reply Aaron Brace
- Re: Restricting RSA Authentication. - Reply Randolph J. Herber
- Re: Restricting RSA Authentication. Shiloh Costa
- Re: Restricting RSA Authentication. Asmodeus
