Movatterモバイル変換


[0]ホーム

URL:


Home page logo
nmap-dev logo

Nmap Developmentmailing list archives

PreviousBy DateNext
PreviousBy ThreadNext

Kazaa/p2pnetworking ports


From: Jake Maul <jakemaul () cox net>
Date: Sat, 09 Aug 2003 21:44:05 -0700

Howdy,
Whilst checking the access log on my router I ran across accesses toport 3531. A little googling leads to the discovery of 2 (4) ports notlisted in nmap-services. Perhaps they could be inserted into thedistributed nmap-services file for the next release as such:
kazaa             1214/tcp   # Kazaa File Sharingkazaa             1214/udp   # Kazaa File Sharingp2pnetworking     3531/tcp   # P2PNetworking/PeerEnabler protocolp2pnetworking     3531/udp   # P2PNetworking/PeerEnabler protocol
3531 might be better named 'PeerEnabler', since that's the name of theproduct and P2PNetworking.exe is the name of the executable. Or thecompany name could be used, "Joltid".
On PC's where Kazaa has been installed and run, P2PNetworking.exe opensup port 3531, and it stays open even if Kazaa is closed (it is aseparate process, and the port is not configurable). If it is notrunning when Kazaa is launched, it will be started- but never stopped.1214 is open only when Kazaa is running, but 1214 is only the defaultport (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 tonmap-dev-help () insecure org . List run by ezmlm-idx (www.ezmlm.org).

PreviousBy DateNext
PreviousBy ThreadNext

Current thread:


[8]ページ先頭

©2009-2025 Movatter.jp