We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
My certificates stopped working after updating my phone to iOS 13.
After some googling I found this page:
https://support.apple.com/en-us/HT210176
So - they will likely also fail in OSX 10.15 when it arrives later this month.
Note that this only affects the host cert's - my CA cert is still working fine.
I had to make two changes to my ca/host.cnf (and to the config.cnf's generated from it)
Current:
[ v3_req ] basicConstraints = CA:FALSE keyUsage = nonRepudiation, digitalSignature, keyEncipherment <<ALT_HOSTNAMES>>
Updated:
[ v3_req ] basicConstraints = CA:FALSE keyUsage = nonRepudiation, digitalSignature, keyEncipherment extendedKeyUsage = serverAuth, clientAuth <<ALT_HOSTNAMES>>
Not sure what you may want to change - the number of days you might want to leave and have a README comment ?
I think the adding of the extendedKeyUsage is OK for everyone - I can see for example my LetsEncrypt certificates all have that.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
My certificates stopped working after updating my phone to iOS 13.
After some googling I found this page:
https://support.apple.com/en-us/HT210176
So - they will likely also fail in OSX 10.15 when it arrives later this month.
Note that this only affects the host cert's - my CA cert is still working fine.
I had to make two changes to my ca/host.cnf (and to the config.cnf's generated from it)
Current:
Updated:
Not sure what you may want to change - the number of days you might want to leave and have a README comment ?
I think the adding of the extendedKeyUsage is OK for everyone - I can see for example my LetsEncrypt certificates all have that.
The text was updated successfully, but these errors were encountered: