Nmap Development mailing list archives
Re: Determining UDP 161 port (SNMP) status using SNMPv3
From: Tom Sellers <nmap () fadedcode net>
Date: Tue, 17 Jun 2008 23:04:37 -0500
I have attached a patch to nmap-service-probes that includes the probe/match combination that I spoke of earlier. It sends a SNMPv3 connection request that with the username sent to "public". The rarity has been set to 4, the same as the SNMPv1public probe. Thanks, Tom
Attachment:
snmpv3_patch.txt
Description:
_______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org
Current thread:
- Determining UDP 161 port (SNMP) status using SNMPv3 Tom Sellers (Jun 17)
- Re: Determining UDP 161 port (SNMP) status using SNMPv3 Fyodor (Jun 17)
- Re: Determining UDP 161 port (SNMP) status using SNMPv3 Tom Sellers (Jun 17)
- Re: Determining UDP 161 port (SNMP) status using SNMPv3 Fyodor (Jun 18)
- Re: Determining UDP 161 port (SNMP) status using SNMPv3 Tom Sellers (Jun 18)
- Re: Determining UDP 161 port (SNMP) status using SNMPv3 - Update patch Tom Sellers (Jun 21)
- Re: Determining UDP 161 port (SNMP) status using SNMPv3 - Update patch Fyodor (Jun 28)
- Re: Determining UDP 161 port (SNMP) status using SNMPv3 Tom Sellers (Jun 17)
- Re: Determining UDP 161 port (SNMP) status using SNMPv3 Fyodor (Jun 17)