Thank you all for the assistance - trying to convince Qt/C++ SSL sockets to do
as you've described by cutting down on ciphers. I did check std Google Chrome
ClientHello which does only contain about 10 cipher suites - where Qt seems to
include a lot more (all supported) - so what i'm trying to
Since this is a MS IIS 7.0 server I would argue that it'd be in the interest of
openssl to handle the situation rather than accept this scenario - since IIS is
likely powering more than a few hosts? It is possible to have the host
correctly list its supported protocols using nmap - i'd assume
Hi there
I've recently come across what looks to be an internal bug in openssl:
Original symptoms was that neither "curl" or "wget" could access the following
site:
https://coverage.tre.se - this site is using TLS 1.0 (only) and does have some
pretty crazy certificate issues - but does show
