Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

More tests with other tools #299

Closed
kazu-yamamoto opened this issue Nov 6, 2018 · 5 comments
Closed

More tests with other tools #299

kazu-yamamoto opened this issue Nov 6, 2018 · 5 comments

Comments

@kazu-yamamoto
Copy link
Collaborator

@kazu-yamamoto
Copy link
Collaborator Author

With kazu-yamamoto/trytls#1, trytls says:

 FAIL protect against the Logjam attack [reject www.ssllabs.com:10445]
      output: 200 OK
 FAIL denies use of 480 bit Diffie-Hellman (DH) [reject dh480.badssl.com:443]
      output: 200 OK
 FAIL denies use of 512 bit Diffie-Hellman (DH) [reject dh512.badssl.com:443]
      output: 200 OK
 FAIL certificate has invalid key usage for HTTPS connection [reject bad-key-usage.badtls.io:11005]
      output: 200 OK
 FAIL denies use of MD5 signature algorithm (RFC 6151) [reject weak-sig.badtls.io:11004]
      output: 200 OK

@kazu-yamamoto
Copy link
Collaborator Author

4th one disappears on master thanks to #274.

@ocheron
Copy link
Contributor

ocheron commented Nov 6, 2018

Also to note we have configurable hook for DH, and MD5 can be addressed with #194.

@vdukhovni
Copy link
Collaborator

MD5 should simply never have been included in signature algorithms. It was a mistake in the TLS 1.2 specification to include a code point for MD5 signatures. The solution is to remove support for the codepoint.

@kazu-yamamoto
Copy link
Collaborator Author

I sent a PR to trytls: ouspg/trytls#312

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants