|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Subject: Re: nmap woes.
From: William Cordis (whcordis
HOST-0080C84B1ED9.PUBLIC.SOUTHERN.EDU)Date: Thu Aug 17 2000 - 21:44:42 CDT
- Next message: Chaosmage: "Re: nmap woes."
- Previous message: Andrew Hatfield: "Re: nmap woes."
- In reply to: Chaosmage: "Re: nmap woes."
- Next in thread: Scott Nursten: "Re: nmap woes."
- Next in thread: JD Conley: "Re: nmap woes."
- Reply: William Cordis: "Re: nmap woes."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Aug 17, 2000 at 03:45:13PM -0700, Chaosmage wrote:
> I explicity said in my email that I am running this scan as root. And I have
> read the nmap man page. I am wondering what kernel option would be
> controling this problem, or if it simply a output ruleset that is too
> strict.
Ok.. I eat crow... what command line opts are you using and what kernel.
I have worked a bit with the program and tried some of the wilder opts
on 2.2 kernels and 2.4. AFAIK the only way to make stock kernels not work
with nmap is to turn off ip networking (all bets are off if your using a
patch or util like LIDS as someone already mentioned). If anything I would say
it is the output rule but it would really be helpfull to see what command line
you are using so I could try to duplicate it on some of the boxes I have here.
Again really sorry for being a stupid moron and not reading. Next time I'll
put more thought into it instead of more kneejerk.
Will
- Next message: Chaosmage: "Re: nmap woes."
- Previous message: Andrew Hatfield: "Re: nmap woes."
- In reply to: Chaosmage: "Re: nmap woes."
- Next in thread: Scott Nursten: "Re: nmap woes."
- Next in thread: JD Conley: "Re: nmap woes."
- Reply: William Cordis: "Re: nmap woes."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]