On Fri, 10 Nov 2000, Kevin D. Clark wrote:
> This isn't strictly security problem. This is actually a combination of
> Its a "how does the OS implement TCP?" problem, combined with some
> fundamental properties of the r(sh|cp|etc) commands.
In other words, RSH/RLOGIN are horribly protocols an
[EMAIL PROTECTED] writes:
> So I've got a bunch of scripts that rsh to systems
> and run some tests. The only problem is the tests
> exectute and close and a new rsh is issued. The rsh
> is refused because it comes in on the same socket as
> the previous one.
Sort-of.
> I'm assuming this is fo
On Thu, 9 Nov 2000, Brian Boerner wrote:
> So I've got a bunch of scripts that rsh to systems
> and run some tests. The only problem is the tests
> exectute and close and a new rsh is issued. The rsh
> is refused because it comes in on the same socket as
> the previous one. I'm assuming this is f
So I've got a bunch of scripts that rsh to systems
and run some tests. The only problem is the tests
exectute and close and a new rsh is issued. The rsh
is refused because it comes in on the same socket as
the previous one. I'm assuming this is for security
purposes. You wouldn't want anyone piggy
