First, thank you so much for mkcert! I love it and use it often ⭐
It seems that some default behavior may have changed in macOS 11, as mkcert isn't working out of the box on GitHub Actions with macos-latest. (Ah yes, I just read an issue I referenced and it said Starting from Big Sur 11.3 certificate installation requires user interaction, however it can be bypassed by using SecItemAdd method.)
I'm getting the same error as reported in #94
And I was advised that I could compile some swift code to solve my issue, similar to what they did in this PR actions/runner-images#3311.
swiftc add-certificate.swift
sudo ./add-certificate YourCertName.cer
By the time I was done, however, I wasn't using mkcert anymore. I thought this would be a more appropriate solution to build into mkcert.
First, thank you so much for mkcert! I love it and use it often ⭐
It seems that some default behavior may have changed in macOS 11, as mkcert isn't working out of the box on GitHub Actions with
macos-latest. (Ah yes, I just read an issue I referenced and it saidStarting from Big Sur 11.3 certificate installation requires user interaction, however it can be bypassed by using SecItemAdd method.)I'm getting the same error as reported in #94
And I was advised that I could compile some swift code to solve my issue, similar to what they did in this PR actions/runner-images#3311.
By the time I was done, however, I wasn't using
mkcertanymore. I thought this would be a more appropriate solution to build into mkcert.