-
Notifications
You must be signed in to change notification settings - Fork 13
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
Add "ech-reject" test case for nss and cloudflare-go #36
Conversation
766eb56
to
78dee24
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only one blocking comment (panic vs return sentinel). The rest looks good!
} | ||
} else { | ||
log.Fatalf("unknown role \"%s\"", *role) | ||
log.Fatalf("Unknown role \"%s\"", *role) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This makes me wonder if we should have a sentinel return value for invalid parameters. @xvzcf, thoughts?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will address this in the follow-up PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See #39, though I'm not sure this totally addresses the point!
In this test case, the client offers ECH using an invalid config, the server rejects, and the client aborts the connection. This adds support for this test case to the nss and cloudflare-go endpoints.
eb8762e
to
f7f009c
Compare
Partially addresses #27.
Adds a test case for exercising the ECH rejection path, with initial support for NSS and Cloudflare-Go.
In this test case, the client offers ECH with an invalid config, the server rejects, and the client aborts the connection with "ech_required" alert. They don't attempt to retry the connection with the retry configs.
Thanks to @kjacobs-moz for help getting the NSS client endpoint right!