Re: Bug#75144: GNOME'e nterm service
Christian Marillat <email@example.com> writes:
> >>>> "SB" == Sergio Brandano <firstname.lastname@example.org> writes:
> SB> Christian,
> SB> I see that you do not have any service in port 1026.
> SB> Are you running GNOME at all?
> I did "rgrep -w nterm *" and "rgrep -w 1026 *" in gnome-libs and gnome-core
> source tree and I find nothing.
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). 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 doesn't make it a bug, a security concern or certainly not a grave
concern. What it does make it is something you should be alerted to; while
in bigger corporate environments you're probably safe (places that use
other workstation things like NIS & NFS firewall all those machines off,
and clueful users firewall themselves off anyway), but it does impact the
`home user' with only one box doing dialup and desktop.
If it's configurable, it should default to Off. (Like it does here,
A big sky above me, | email@example.com
West winds blow. | http://piglet.is.dreaming.org