Howdy,
Whilst checking the access log on my router I ran across accesses to
port 3531. A little googling leads to the discovery of 2 (4) ports not
listed in nmap-services. Perhaps they could be inserted into the
distributed nmap-services file for the next release as such:
kazaa 1214/tcp # Kazaa File Sharing
kazaa 1214/udp # Kazaa File Sharing
p2pnetworking 3531/tcp # P2PNetworking/PeerEnabler protocol
p2pnetworking 3531/udp # P2PNetworking/PeerEnabler protocol
3531 might be better named 'PeerEnabler', since that's the name of the
product and P2PNetworking.exe is the name of the executable. Or the
company name could be used, "Joltid".
On PC's where Kazaa has been installed and run, P2PNetworking.exe opens
up port 3531, and it stays open even if Kazaa is closed (it is a
separate process, and the port is not configurable). If it is not
running when Kazaa is launched, it will be started- but never stopped.
1214 is open only when Kazaa is running, but 1214 is only the default
port (user-configurable).
There's a short and sweet thread about this:
http://lists.jammed.com/incidents/2003/07/0045.html
---------------------------------------------------------------------
For help using this (nmap-dev) mailing list, send a blank email to
nmap-dev-help_at_insecure.org . List run by ezmlm-idx (www.ezmlm.org).
Received on Aug 10 2003
Intro
