-
Notifications
You must be signed in to change notification settings - Fork 7
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
Verify PSC DNS name is present as a SAN in the server certificate #324
Labels
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: cleanup
An internal cleanup or hygiene concern.
Comments
nancynh
added
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: cleanup
An internal cleanup or hygiene concern.
labels
Jun 11, 2024
is this a duplicate of #313 ? |
Yes, let's use this one for tracking. |
Good context on the trailing dot being stripped dpkp/kafka-python#2374 (comment) |
More good context on this thread: openssl/openssl#11560 |
Thanks to @jackwotherspoon for finding this: openssl/openssl#11560 (comment) TL;DR: SANs shouldn't have trailing dots. |
RFC 6066 says no trailing dots in SANs. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: cleanup
An internal cleanup or hygiene concern.
Verify PSC DNS name is present as a SAN in the server certificate. It means removing the existing workaround to check the private IP address instead of the DNS name (#291).
The text was updated successfully, but these errors were encountered: