tls1.2 not detected while available.

[underdarknl]

For some host, eg: werkbezoek.minvws.nl tls1.2 is not found, while it is availabe according to other tests.

[jtesta]

Thanks for reporting this! And big thanks for including a publicly-available target for me to debug this issue with!

I've just submitted PR #335 which addresses this issue.

Might you know what the TLS stack on that target host is running? Its refusal to respond to our handshakes likely violates the TLS spec, so I'm very curious to know what it is.

[underdarknl]

Ill see if I can poke around and ask what stack they are using. If I find out i'll let you know.
Is there any tooling that you know of that would recognize these violations of the spec and report on them?

[jtesta]

I don't know of anything that would behave like this, no.

[underdarknl]

Sadly, I've yet to find out the actual webserver doing the TLS interactions.

Could you tag a new release with this change so we can include it in our scanners in OpenKAT?

[rbsec]

If you ever do find out then let us know - more out of curiosity than anything else.

There were some significant (and potentially build-breaking) changes in #326 which has recently been merged, so that'll be version bump up to 2.2.x rather than just a minor version change. As part of that I'd like to get #331 merged and #333 implemented as well as part of that (hopefully next week, as I'm away at the moment) - so once those are sorted I'll tag a new release as 2.2.0.

[rbsec]

@underdarknl sorry for the delay - this change is now part of the 2.2.0 tag that's just been made.