-
-
Notifications
You must be signed in to change notification settings - Fork 181
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
MacOS keychain trust not as expected #101
Comments
For completeness, here's the certificate:
|
First, install openssl (v3), then create any folder that be contains your certificates. Open shell and enter: "mkdir CA && mkdir Localhost". Generate CA:
Generate for Localhost usage (macOS):
Install CA and use Localhost certificate on your localhost server. The problem is long period. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I had some issue with certificates on my home DNS today, and thought I'd use
dog
to debug. I'm using version 0.1.0.My scenario was that the TLS certificates had expired, and I caught that fairly quickly. Renewed the certs and got them in place. Then tried to validate with
dog
and it helped me identify the next issue, which was that I only updated one of the pair of servers. After updating that, I hoped fordog
to confirm I had the fix, but still wasn't quite there.Trying to verify the fix, I turned again to
dog
and was disappointed:Dug in a bit to see what might be up, and thought maybe it was because Mac didn't trust the roots. That wasn't the case, they're all set.
Tried to present the intermediate with the cert…CoreDNS doesn't let me do that so I was out of luck. So I made sure my Mac trusted the intermediate
Tried again and still no luck
I switched over to
kdig
for a sanity check, and it seems to be reading my trust settings correctly.I'm running on MacOS Monterrey, v 12.3.1, and here's the details from
uname
.The text was updated successfully, but these errors were encountered: