Closed joente closed 1 year ago
Describe the bug TCP Probe collector version 3.0.2 contains an image where nmap is not always giving the desired result:
nmap
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE nmaprun> <?xml-stylesheet href="file:///usr/bin/../share/nmap/nmap.xsl" type="text/xsl"?> <!-- Nmap 7.80 scan initiated Fri Sep 22 07:57:20 2023 as: nmap --script +ssl-cert -oX - -p 443 +ssl-enum-ciphers 192.168.1.2 --> <nmaprun scanner="nmap" args="nmap --script +ssl-cert -oX - -p 443 +ssl-enum-ciphers 192.168.1.2" start="1695369440" startstr="Fri Sep 22 07:57:20 2023" version="7.80" xmloutputversion="1.04"> <scaninfo type="syn" protocol="tcp" numservices="1" services="443"/> <verbose level="0"/> <debugging level="0"/> Failed to resolve "+ssl-enum-ciphers". <host starttime="1695369440" endtime="1695369470"><status state="up" reason="echo-reply" reason_ttl="63"/> <address addr="192.168.1.2" addrtype="ipv4"/> <hostnames> </hostnames> <ports><port protocol="tcp" portid="443"><state state="open" reason="syn-ack" reason_ttl="63"/><service name="https" method="table" conf="3"/></port> </ports> <times srtt="213" rttvar="3757" to="100000"/> </host> <runstats><finished time="1695369470" timestr="Fri Sep 22 07:57:50 2023" elapsed="30.34" summary="Nmap done at Fri Sep 22 07:57:50 2023; 1 IP address (1 host up) scanned in 30.34 seconds" exit="success"/><hosts up="1" down="0" total="1"/> </runstats> </nmaprun>
Expected behavior It seems that "+ssl-enum-ciphers" cannot be resolved. The expectation is for nmap to either return with an error, of with the desired result.
"+ssl-enum-ciphers"
This issue is solved in v3.0.3, just by updating the image with a new build.
Describe the bug TCP Probe collector version 3.0.2 contains an image where
nmap
is not always giving the desired result:Expected behavior It seems that
"+ssl-enum-ciphers"
cannot be resolved. The expectation is for nmap to either return with an error, of with the desired result.