Verify your certificates are being issued for no more than 27 months (825 days to be exact) 2

[jimbojimbo]

Certificates issued after July 1st 2019 with a validity period of greater then 825 days are going to give you a headache with the upcoming release of iOS-13, macOS-10.15 and Android-Q. Additionally, the DNS will be required in the Subject Alternate Name (SAN) extension even if the DNS matches the common name. You need to take a proactive look at your environment if using iOS and Android devices. System Manager defaults may have been changed. The validity period for certificates has changed in the CA Browser Forum spec and currently sits at 27 months.. As all vendors are becoming more security conscious they are aligning policies with public CA requirements. This may have an impact on your internal Certificate Authorities including System Manager.

 

[kyle555]

You, sir, are doing the lord's work. Thank you.

 

[dialtonebone]

https://downloads.avaya.com/css/P8/documents/101058839

<<Avaya PSN mentioning this.

Thanks for sharing, I would have no idea this was a rule currently in affect without the post.

 

[kyle555]

https://community.letsencrypt.org/t/signed-certificate-timestamps-embedded-in-certificates/57187

https://www.certificate-transparency.org/how-ct-works

https://support.apple.com/en-ca/HT205280

Anyone hear anything else about this?

The Apple link says that certs can be longer, but require more SCTs. I read that as meaning a 'secure certificate timestamp' is a thing the CA issuing you your cert provides in your certificate. It's another layer of validation. Instead of just being "the godaddy CA issued this cert" it also means "godaddy submitted this to the Google or whatever else certificate transparency log and got these stamps for you'.

Looks like the more stamps you got, the longer your cert can be good as far as Apple's concerned. And it might be only 15 months if you don't have enough signed cert stamps.