The 'Security Digest' Archives (TM)

Archive: About | Browse | Search | Contributions | Feedback
Site: Help | Index | Search | Contact | Notices | Changes

ARCHIVE: 'Phage List' - Archives (1988 - 1989)
DOCUMENT: phage #290 [Re: ~uucp/.forward] (1 message, 532 bytes)
SOURCE: http://securitydigest.org/exec/display?f=phage/archive/290.txt&t=text/plain
NOTICE: securitydigest.org recognises the rights of all third-party works.

START OF DOCUMENT

From: der Mouse <mouse@larry.mcrcim.mcgill.edu>
To: phage
Date: Mon 02:20:32 21/11/1988 EST
Subject: Re: ~uucp/.forward
References: [Thread Prev: 289] [Thread Next: 293] [Message Prev: 289] [Message Next: 292]

> Don't forget that if you can write into ~uucp/.forward, you can also
> write into ~uucp/.rhosts

But that doesn't buy you much, because rlogin/rsh/rcp (the things that
use .rhosts) all use the user's shell.  Rlogin will give you a uucp
connection, such as you might get by telnetting to the uucp port.  Rsh
likewise, with a complaint about the -c option passed by the daemon.
Rcp doesn't work any better.  (I just tried all three.)  Or do .rhosts
files control something else that hasn't occured to me yet?

					der Mouse

			old: mcgill-vision!mouse
			new: mouse@larry.mcrcim.mcgill.edu

END OF DOCUMENT