On Mon, Oct 30, 2000 at 15:27 +0100, Anibal Vasquez wrote:
Roman Drahtmueller wrote:
[ ... why you can't bind to a socket already in use ... ]
Wow, thanks a lot! If I understand it right, this would also apply to the xdm running on my machine, so it´s not possible for a user to listen to any local port (on the machine running xdm) used by xdm for an existing X-connection to an X-terminal.
Yes, you cannot listen to an ongoing connection over a socket you don't own (unless you can read the kernel's buffer for the socket, but if you can do this ...). All one could do is to setup another machine with a promiscous interface catching all the traffic. That's why physical security is just as important as secured software is, when you're serious about it.
Thanks! Does this topic have a name? I mean, what should I search the web for in order to get info like this? (So I don´t need to post it here :)
Try to read "man 2 socket" and follow the "SEE ALSO" section. "man 2 bind" will tell you about reasons why this could fail. One of those is "[EADDRINUSE] The specified address is already in use." Doc is not always "on the web". Sometimes (more often than one thinks) it's even on your local disk. :> virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you.