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

Option to enable PermittedDNSDomains #26

Open
JustinAzoff opened this issue Apr 20, 2019 · 2 comments
Open

Option to enable PermittedDNSDomains #26

JustinAzoff opened this issue Apr 20, 2019 · 2 comments

Comments

@JustinAzoff
Copy link

Hi!

Would you accept a PR that adds an option to fill in PermittedDNSDomains?
I verified it works if I just add 2 lines to the template:

    PermittedDNSDomainsCritical: true,
    PermittedDNSDomains: []string{".local", ".me.dev"},

Then if I try to generate a cert for google.com it fails validation:

$ ./minica -domains google.com
$ openssl verify  -CAfile minica.pem  google.com/cert.pem 
CN = google.com
error 47 at 0 depth lookup: permitted subtree violation
error google.com/cert.pem: verification failed

It'll take a bunch of changes to pass a new CLI option all the way up to makeRootCert

@jsha
Copy link
Owner

jsha commented Apr 20, 2019 via email

@JustinAzoff
Copy link
Author

I have.. minica is what I'm looking for (easy ssl certs for local services and IoT crap). mkcert has the same issue with not being able to limit the scope of the CA anyway.

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

2 participants