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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Other requests response exception #195

Open
jsf9k opened this issue Jun 20, 2019 · 2 comments
Open

Other requests response exception #195

jsf9k opened this issue Jun 20, 2019 · 2 comments
Assignees
Labels
bug This issue or pull request addresses broken functionality
Projects

Comments

@jsf9k
Copy link
Member

jsf9k commented Jun 20, 2019

馃悰 Bug Report

When performing pshtt scanning, sometimes we get an error in AWS Lambda stating "other requests response exception". In this case we do not receive scan results for the domain that errored.

To Reproduce

caats3.va.gov is a domain where this happens often.

Expected behavior

A successful scan.

Any helpful log output

None.

@jsf9k jsf9k added the bug This issue or pull request addresses broken functionality label Jun 20, 2019
@jsf9k jsf9k self-assigned this Jun 20, 2019
@jsf9k jsf9k added this to To do in BOD 18-01 Jun 20, 2019
@echudow
Copy link
Collaborator

echudow commented Jul 30, 2019

@jsf9k I wonder if this has to do with the breaking change in sslyze v2.1.0 in early June where they changed how certificate verification works and so a number of the fields in the certificate plugin went away. I think there were some missing attribute exceptions. See the commits in my fork at echudow@c2f427b and echudow@ce0ccaf for how I addressed this issue with some workarounds to handle both the older and newer versions of sslyze. We're still testing those changes though.

@jsf9k
Copy link
Member Author

jsf9k commented Aug 1, 2019

@echudow This issue can't be due to that, since the pshtt lambda hadn't been rebundled since May. Thanks for mentioning that, though, since it will be a problem now (as I'm rebundling to deploy the logging improvements in #197, which will pull in a newer sslyze).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue or pull request addresses broken functionality
Projects
Status: To do
BOD 18-01
  
To do
Development

No branches or pull requests

2 participants