Open warburtr0n opened 3 years ago
Although Cryptonice v1.4.0.1 isn't producing an error, it is producing odd outputs. i.e. TLS is available and a TLS fingerprint is available, but not cipher, protocol or cert info is available:
Pre-scan checks
-------------------------------------
Scanning buzzfeed.com on port 443...
Analyzing DNS data for buzzfeed.com
Fetching additional records for buzzfeed.com
buzzfeed.com resolves to 13.224.84.4
13.224.84.4:443: OPEN
TLS is available: True
Connecting to port 443 using HTTPS
Reading HTTP headers for www.buzzfeed.com
RESULTS
-------------------------------------
Hostname: www.buzzfeed.com
Selected Cipher Suite: None
Selected TLS Version: None
Supported protocols:
TLS fingerprint: 29d29d00029d29d00041d41d00041d69337e5f535144f26f5d7e01b189f9d0
HTTP to HTTPS redirect: True
HTTP Strict Transport Security: True (max-age=31536000; preload)
None
For example buzzfeed.com
cryptonice buzzfeed.com --scans tls dns http jarm --tls all
This one is simply that the certificate_info key isn’t set.
That’s likely due to tls_data = tls_scan(ip_address, str_host, commands_to_run, port) not always setting it.