Skip to content

Option to enable PermittedDNSDomains #26

Open

Description

@JustinAzoff

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

Activity

  1. jsha commented on Apr 20, 2019

    @jsha
    Owner
  2. JustinAzoff commented on Apr 20, 2019

    @JustinAzoff
    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.

  3. petkov commented on Dec 12, 2024

    @petkov

    Was looking for the same option, so ended up using openssl instead. Here is the guid that I used: https://github.com/petkov/homeassistant/wiki/Creating-root-CA-and-enabling-HTTPS-in-HomeAssistant

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions