Re: Bug#75144: GNOME'e nterm service
On Thu, Oct 19, 2000 at 06:02:14PM +0100, Sergio Brandano wrote:
> >actually i dont think it is really relevant what nterm really is, cos
> >that is just something nmap came up with.
> It is relevant because it is a tcp service that I may NOT want to
> give or use, because it is running on my machine, because I am
> And actually no, it has nothing to do with nmap. nmap is just a port
---end quoted text---
I think what your misunderstanding here is what nmap is telling you and how it works.
Yes, this has everything to do with nmap.
nmap is just a port scanner. nmap comes with a file ("nmap-services" if I remember correctly) which has a long list of port numbers associated with the names of programs that are most commonly found running on those ports from the author's experience. apparantly there is a program called nterm out there somewhere which often runs on port 1026. this program may run on linux systems, but it may not, it may be a windows program that uses that port, or a mac program that uses that port. The thing to keep in mind is that nmap has no way of telling what programs are being run on a certain port, all it can tell is if a port is open or not, and when it finds one that's open it tells you it's open, and tells you what program MAY be using that port.
netstat on the other hand (which you used earlier) can tell you exactly what program is running on a specific port. and netstat told you it was gnome-session. so gnome-session is the program you should be researching. nterm has absolutely NOTHING to do with what your reporting.
I hope this clearifies matters for you.
Brian Johnson <firstname.lastname@example.org>
Software undergoes beta testing shortly before it's released.
Beta is Latin for still doesn't work.