-
Notifications
You must be signed in to change notification settings - Fork 88
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
Update TLS Observatory Parser Linting: Cert Lint into TLS Observatory #257
Milestone
Comments
I'd be open to trying this. Would Would this be in a new worker? (Either one worker per cert lint tool or all tools under one worker.) |
I think this would be a new worker, probably similar to |
adamdecaf
added a commit
to adamdecaf/tls-observatory
that referenced
this issue
Mar 25, 2018
adamdecaf
added a commit
to adamdecaf/tls-observatory
that referenced
this issue
Mar 25, 2018
adamdecaf
added a commit
to adamdecaf/tls-observatory
that referenced
this issue
Mar 25, 2018
adamdecaf
added a commit
to adamdecaf/tls-observatory
that referenced
this issue
Mar 25, 2018
Merged
adamdecaf
added a commit
to adamdecaf/tls-observatory
that referenced
this issue
Mar 25, 2018
adamdecaf
added a commit
to adamdecaf/tls-observatory
that referenced
this issue
Apr 9, 2018
adamdecaf
added a commit
to adamdecaf/tls-observatory
that referenced
this issue
Apr 9, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Similar but different to #187, this is to integrate the AWS Labs Cert Lint tool's output into the certificate parser's output.
The integration is expected to be via a shell execution of the other utility. If we need to do something more exotic (RPC to a Docker instance, for example), that should be a follow-up. For now, this issue should assume we can call out to the executable and read the results from
stdout
.The text was updated successfully, but these errors were encountered: