Comment on Decreasing Certificate Lifetimes to 45 Days
Unforeseen@sh.itjust.works 1 week agoNo, because it’s no longer dangerous if it’s trusted.
You give your friends your public root and if applicable, intermediary certs. They install them and they now trust any certs issued by your CA.
Source: I regularly build and deploy CA’s in corps
Valmond@lemmy.world 1 week ago
Thank you!
Is there some simple soft that let you make those certs, like with a root cert and then “derived” certs? On linux :-) ?
I guess people have to re-trust every now and then because certs get old, or do they trust the (public partof the) root cert and the daughter certs derived from root are churned out regularly for the sites?
Unforeseen@sh.itjust.works 1 week ago
Openssl can do everything.
That’s right, but instead of the word derived we use “issued”
Correct certs get old by design, they can also be revoked. As another commenter mentioned the biggest pain is actually in the redistribution of these end certificates. In enterprise this is all managed usually with the same software they use for deployment or have auto enrollment configured.
You should find tons of guides just take it slow to understand it all. Understanding certificates in depth is a rare and good skill to have. Most sysadmins I come across are scared to death of certificates.
Valmond@lemmy.world 1 week ago
I was forced to learn some of it at work (using and signing medical payment transactions, with x509 certificates) so I have ar least a starting point. I have no idea how the revoke process works though, I can’t figure out a way that it functions without a central authority getting queried regularly. I thonk I can start without that knowledge though.
Anyway, with your information I’m up and running, thank you again!
“Derived certificates” not child certs, noted !