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

X509v3 Subject Alternative Name must be critical #533

Open
seregaizsbera opened this issue Jun 22, 2023 · 0 comments
Open

X509v3 Subject Alternative Name must be critical #533

seregaizsbera opened this issue Jun 22, 2023 · 0 comments

Comments

@seregaizsbera
Copy link

Environment

  • Operating system (including version):
    any

  • mkcert version (from mkcert -version):
    1.4.4

  • Server (where the certificate is loaded):
    any

  • Client (e.g. browser, CLI tool, or script):
    OpenDJ 3.5

What you did

Consider legacy soft that expected the server name to match certificate's common name.

What went wrong

That soft issues verification error, since real name of the server resides in SAN Extension.

The Certificate presented by the server example.com could not be trusted. There is a name mismatch between the name of the server (example.com) and the subject DN of the certificate. This could be caused because you are connected to a server pretending to be example.com. Before accepting this certificate, you should examine the server's certificate carefully.

Expected result

If mkcert doesn't allow deprecated usage of common name field in subject, it must specify, that SAN extension is critical, so that legacy soft doesn't try to use it in deprecated way. The error message would be something like 'unsupported certificate purpose'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant