-
Notifications
You must be signed in to change notification settings - Fork 60
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
IPv6 address not regarded as a valid CN #37
Comments
sjoerdsimons
added a commit
to sjoerdsimons/dynamiclistener
that referenced
this issue
Jun 11, 2021
Expand the cnRegexp to also accept ipv6 addresses such as: * ::1 * 2a00:1450:400e:80e:: * 2a00:1450:400e:80e::200e Fixes: rancher#37 Signed-off-by: Sjoerd Simons <sjoerd@collabora.com>
This was referenced Jun 11, 2021
brandond
pushed a commit
to brandond/dynamiclistener
that referenced
this issue
Jun 14, 2021
Expand the cnRegexp to also accept ipv6 addresses such as: * ::1 * 2a00:1450:400e:80e:: * 2a00:1450:400e:80e::200e Fixes: rancher#37 Signed-off-by: Sjoerd Simons <sjoerd@collabora.com> (cherry picked from commit dc7452d)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using k3s on an dual-stacked system i'm seeing message like:
This is caused by the dynamic listener CN check not regarding raw ipv6 address as valid CN names
The text was updated successfully, but these errors were encountered: