Re: Locking down ssh config in large env

Would everybody on this mailing list please stop using autoresponders
that respond to list messages.  Thank you.  I really don't need to know
that some part of the readership is on vacation.  This seems to be most
apparent on Lotus Notes and Exchange mail systems.

Brett Anderson suggested:

> Perhaps you could create the .ssh files for them, have the .ssh files
> owned by another user(i.e. root), and don't give the end-user's write
> privileges.

If you do this, you also need to modify the ssh source code so that it
won't have hangups about somebody else owning those files.

If the users can bring in their own binaries, they can always modify
the name of the expected .ssh directory in the code so this is not a
solution to that problem either.

-- 
Atro Tossavainen (Mr.)               / The Institute of Biotechnology at
Systems Analyst, Techno-Amish &     / the University of Helsinki, Finland,
+358-9-19158939  UNIX Dinosaur     / employs me, but my opinions are my own.
< URL : http : / / www . helsinki . fi / %7E atossava / > NO FILE ATTACHMENTS