Nmap Development mailing list archives
ncat ssl insecure?!
From: Zibri <zibree () gmail com>
Date: Sat, 21 Jan 2017 01:17:03 +0200
connecting using google chrome to ncat ( gives an insecure error: The connection to this site uses a strong protocol (TLS 1.2), an obsolete key exchange (RSA), and a strong cipher (AES_128_GCM). obviously it can be manually ignored but it's annoying... I run ncat in this way: ncat -lk -p 8084 --ssl --ssl-cert=cert.pem --ssl-key=privkey.pem -c ./myscript.sh is there any way to avoid it or is it a problem that must be addressed by you? regards, Zibri
_______________________________________________ Sent through the dev mailing list https://nmap.org/mailman/listinfo/dev Archived at http://seclists.org/nmap-dev/
Current thread:
- ncat ssl insecure?! Zibri (Jan 21)
- Re: ncat ssl insecure?! Daniel Miller (Jan 21)