Nmap Security Scanner
*Intro
*Ref Guide
*Install Guide
*Download
*Changelog
*Book
*Docs
Security Lists
*Nmap Hackers
*Nmap Dev
*Bugtraq
*Full Disclosure
*Pen Test
*Basics
*More
Security Tools
*Pass crackers
*Sniffers
*Vuln Scanners
*Web scanners
*Wireless
*Exploitation
*Packet crafters
*More
Site News
Site Search:
Exploit World
Advertising
About/Contact
Credits
Sponsors:

Vulnerability Development mailing list archives

Re: Interesting "hosts" & "services" issue
From: Bluefish <11a () GMX NET>
Date: Thu, 10 Aug 2000 16:03:51 +0200
Wouldn't specifying a port number to listen in on the code of the
actual trojan result in achieving this? EG. If you created the trojan to
listen in on port 139 wouldn't netstat see this as a nbsession
thing-a-ma-jiggy or so? Something like...


yes :)

..:::::::::::::::::::::::::::::::::::::::::::::::::..
     http://www.11a.nu || http://bluefish.11a.nu
    eleventh alliance development & security team

  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]