Open prologic opened 2 years ago
Not sure never used this tool was just checking it out, but normally *.home.arpa does not cover home.arpa, you would need to specify both in the request. Again not sure if possible here, but that would likely solve the problem.
Yes, supported like this
minica --domains '*.foo.com,foo.com'
Yes, supported like this
minica --domains '*.foo.com,foo.com'
You are correct! This was just a bad invocation on my part 😆
I tried this ./minica --domains '*.home,home'
for https://bitwarden.home/. It didn't match.
I get NET::ERR_CERT_COMMON_NAME_INVALID
Is there something I should do?
I tried this
./minica --domains '*.home,home'
for https://bitwarden.home/. It didn't match. I get NET::ERR_CERT_COMMON_NAME_INVALID Is there something I should do?
Same issue, minica does not support first level wildcard cert, you need use *.bitwarden.home,bitwarden.home
as a domain arg
I see a PR https://github.com/jsha/minica/pull/45 that adds a -common flag to the cli but I'm not actually sure if this will help
Yes - it is exactly reason why this PR wait for merging ...
According to the README wildcard certs are supported.
But I've just tried this and Chrome (at least) gets an error:
Similar errors appear in a Go project that uses minica here:
What am I missing? I see a PR #45 that adds a
-common
flag to the cli but I'm not actually sure if this will help?