Re: /etc/hosts.equiv

Mike Segel <mikey@segel.NOSPAM-.KING.OF.MYDOMAIN.-NOSPAM.com> wrote: > Both the use of .rhosts and hosts.equiv are > security holes. > DO NOT USE .rhosts! Check out your man page for rlogind. There MAY be some security enhancements to .rhosts that your OS may have added. For instance, newer versions of Sequent's DYNIX/ptx has a "-R" option for rlogind which forces ruserok() to require that the .rhosts file is owned by root and is only writable by root. At least you have a little more protection, until root gets broken into. > Bill Ennis wrote: > > > > This can be done at a more atomic level in each users .rhosts > > file on the server machine. The format of the .rhosts file > > is: > > machine user > > > > } > > } I/Net v7.2 for Windows requires you to setup an hosts.equiv file. Under > > } I/Net v5.01, the hosts.equiv file was not required because the "trusted" > > } login was managed by I/Net. > > } > > } I guess the easy to grant remote access to all clients is to place a "+" > > } in hosts.equiv. To me, it seems like a security whole! With a large > > } end-user population, how do you manage the hosts.equiv file? Do you > > } need the hosts.equiv file? > > } > > } Steve Romankiw > > } Executive Risk Inc. > > } -- Roger J. Allen Rush-Presbyterian-St. Luke's Medical Center System Administrator Chicago, IL USA Surgical Information Systems Voice: (312)-942-4825 Internet: rja@sis.rpslmc.edu FAX: (312)-942-3036