Re: do we really need all these SNMP scripts?

["Bob Radvanovsky" <rsradvan () unixworks net>]

I, for one, agree with you.  I figured that one of the reasons why you submitted to this mailing list your inquiry is 
because of some of the recent NSE script submissions for non-IT related devices (SCADA).

To be honest with you (and others on this list), I always thought that we needed to have unique code design, etc., 
etc., so I was under the impression that I was to create my own NSE scripts accordingly.

Now...I'm told that I don't need to do that.  I'm *all* for "simplicity".  if we can create an arrayed matrix with 
keyword info that we're looking for, all the more of the reason for creating such a database.  ;)

-rad


At Fri, 4 Feb 2011 20:53:52 +0000, you wrote:
> i was curious. i noticed there are now about 4 or 5 different scripts that each dump different info related to SNMP. i 
> was wondering why we needed to go this route. it seems to me a tool like SNMP-utils (snmpwalk to be specific) would 
> simply be able to accomodate  what everyone was trying to do with their scripts. why not have a complete NSE script 
> like an SNMP walk utility that dumps everything at once and walks all MIBS, instead of going through and making each 
> individual script for specific MIB info. you could simply set a verbosity range and have flags for each output you 
> wanted, instead of a bunch of scipts that really all do the same thing, just dumping different info. i hope this 
> doesn't sound too confusing and i hope it makes sense. it does to me anyway
>
> m|ke                                     
> _______________________________________________
> Sent through the nmap-dev mailing list
> http://cgi.insecure.org/mailman/listinfo/nmap-dev
> Archived at http://seclists.org/nmap-dev/



_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/