>I suspect it's determined more by the corba layer, or something of that
>ilk, at startup-time. It would be more to the point if you did
> $ sudo netstat -pant | grep LIST | grep -Ei 'gnome|session'
>
>I think it's something Sergio's running as part of gnome-session, if not
>the session itself, that's opening up a listener on the lowest port it can
>(above 1024).
I now remember that there was a relation between nterm and "orbit",
but never managed to get it through.
> 1026 is not defined except in nmap (meaning nmap's authors
>have got the impression that a listener is `nterm', so forget that for
>authoritative), and its usage is probably not fixed.
That's another issue.
> That doesn't make it a bug, a security concern or certainly not a
> grave concern.
I believe we are repeating here. The bug I filed is on the lack of
documentation on the issue, and the confusing situation on nterm
and gnome-session. I am running this thing on my machine; as such,
I want to be able to read what it is all about and, eventually,
disable it/tune it.
Sergio
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
