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

Jump to bottom

crypto/tls: run BoringSSL test suite (BoGo) #51434

Open
FiloSottile opened this issue Mar 2, 2022 · 2 comments
Open

crypto/tls: run BoringSSL test suite (BoGo) #51434

FiloSottile opened this issue Mar 2, 2022 · 2 comments
Assignees
@FiloSottile
Labels
NeedsFix The path to resolution is known, but the work has not been done. Testing An issue that has been verified to require only test changes, not just a test failure.
Milestone
Backlog

Comments

@FiloSottile
Copy link
Contributor

BoringSSL has an extensive TLS test suite with a mechanism to run it against other TLS stacks. We should hook it up to crypto/tls.
@FiloSottile FiloSottile added Testing An issue that has been verified to require only test changes, not just a test failure. NeedsFix The path to resolution is known, but the work has not been done. labels Mar 2, 2022
@FiloSottile FiloSottile added this to the Go1.19 milestone Mar 2, 2022
@FiloSottile FiloSottile self-assigned this Mar 2, 2022
@ianlancetaylor
Copy link
Contributor

CC @golang/security

Looks like this didn't make 1.19. Moving to Backlog. Please recategorize as appropriate. Thanks.

@ianlancetaylor ianlancetaylor modified the milestones: Go1.19, Backlog Jun 24, 2022
@FiloSottile
Copy link
Contributor Author

In the same vein, we should consider running the https://github.com/tlsfuzzer/tlsfuzzer test suite, too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@FiloSottile FiloSottile

Labels
NeedsFix The path to resolution is known, but the work has not been done. Testing An issue that has been verified to require only test changes, not just a test failure.
Projects
Release Status & Blockers (1.20)
Status: No status
Milestone
Backlog
Development

No branches or pull requests
2 participants
@FiloSottile @ianlancetaylor