hosts.equiv question
Posted in 1999
Topics: General Discussion
Hi, I'm not sure whether this has come up before, but is it possible to allow access to sqlexecd without adding an entry into hosts.equiv? My problem is, adding the remote host into hosts.equiv allows gives that host access to services like rshd, rlogin etc which in my case is not desirable. Thanks, -- Darren Kelly Steadycom Pty Ltd Senior Support Engineer http://www.steadycom.com.au mailto:dpkelly@steadycom.com.au
Darren Kelly wrote: > Hi, > > I'm not sure whether this has come up before, but is it possible to > allow access to sqlexecd without adding an entry into hosts.equiv? > > My problem is, adding the remote host into hosts.equiv allows gives > that host access to services like rshd, rlogin etc which in my case > is not desirable. > Awhile back I used to use an obscure feature of a ".netrc" file in my home directory which had the format: machine <full host path> login <login to use> password <the password to use> ie 37->cat ~/.netrc machine dbcentre.dom.hp.com login dbownr password foo234.t Obviously storing an unencrypted password this way is just as bad as the problem you have with host.equiv. We typically use .rhosts files. These offer a bit more control, but the security powers do not like them either. -- -------------------------------------------------------------------------- Philip Walden Hewlett Packard Supply Chain Information Systems 1501 Page Mill Road, M/S 5L-A Palo Alto, CA 94304 (415) 857-3899 FAX (415) 857-8234 http://www.scis.hp.com/~pwalden mailto:phil_walden@hp.com --------------------------------------------------------------------------