Skip to content
This repository has been archived by the owner on Jan 2, 2024. It is now read-only.

tlschecker still uses sslyze 0.7 for Strict TLS header checking #8

Closed
anttivs opened this issue Aug 12, 2014 · 1 comment
Closed

tlschecker still uses sslyze 0.7 for Strict TLS header checking #8

anttivs opened this issue Aug 12, 2014 · 1 comment
Assignees
@anttivs
Labels
bug
Milestone
End of 2014 release

Comments

@anttivs
Copy link
Contributor

anttivs commented Aug 12, 2014

Needs to be updated to do that for 0.8/0.9 output. Currently users just need to disable that check.
@anttivs anttivs added the bug label Aug 12, 2014
@anttivs
Copy link
Contributor Author

anttivs commented Aug 13, 2014

Apparently it does work for 0.8, but only if the HTTP connection succeeds. If the HTTP connection fails, sslyze's XML output lacks an element, which throws Mittn's XML parsing off. Have to check whether sslyze 0.9 has a fix, and if not, need to patch around it.

@anttivs anttivs added this to the End of 2014 release milestone Oct 31, 2014
@anttivs anttivs self-assigned this Oct 31, 2014
@anttivs anttivs closed this as completed in 4825fe1 Dec 4, 2014
anttivs pushed a commit that referenced this issue Dec 4, 2014
Merge pull request #5 in SWSEC/mittn from bugfix/sslyze-update to master
1efa883 
* commit '4825fe1321af19a3a3d5413662c3ab4dc4f4e669':
  Support sslyze 0.10. Closes #7, closes #8.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@anttivs anttivs

Labels
bug
Projects
None yet
Milestone
End of 2014 release
Development

No branches or pull requests
1 participant
@anttivs