[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Freeipmi-devel] Re: GE rsh problem
From: |
Anand Babu |
Subject: |
Re: [Freeipmi-devel] Re: GE rsh problem |
Date: |
Wed, 04 Aug 2004 12:49:03 -0700 |
User-agent: |
Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux) |
,----[ Ian Zimmerman <address@hidden> ]
| ab> Please run gdb (or at least strace) to figure out who (xinetd or
| ab> in.rshd) opens these new free ports per connection and why. Look
| ab> for open ports both on server and client.
|
| Albert> I believe both in.rshd (through rresvport()) and rsh (through
| Albert> rcmd(), which subsequently calls rresvport()) use sockets with
| Albert> privileged ports.
|
| The mystery part is solved: rsh protocol uses _two_ connections, the
| additional one (for standard error) from the server to the client,
| with a source port allocated by rresvport.
`----
Good trace. Thanks Al and Ian.
,----[ Ian Zimmerman <address@hidden> ]
| Now, why isn't the blocking daemon working to make the two ports
| EADDRINUSE?
`----
Yes, that is what the daemon is trying to achieve indirectly. By
opening the reserved ports in advance, Kernel will automagically
return EADDRINUSE to the rest of the world. This was the simplest fix
I can think about in user space without requiring a patch to the
kernel or rsh. Any better ideas are most welcome.
,----[ Ian Zimmerman <address@hidden> ]
| I think the ball is in Mr. Manian's court.
`----
Yes, We are waiting to hear from Anand Manian. Please ask Pradhap to
give him a call.
--
Anand Babu
Free as in Freedom <www.gnu.org>