2 ms·
But a Certificate isn't a CSR. CAs can do whatever magic they want here†, but, they probably shouldn't. If you're comfortable keeping the same keys, which, su
by tialaramex 5y ago
But a Certificate isn't a CSR.
CAs can do whatever magic they want here†, but, they probably shouldn't.
If you're comfortable keeping the same keys, which, sure, in some situations is fine (although a loss of agility can hurt you if you didn't understand what you were doing and then have to change keys unexpectedly) you can use the same CSR over and over to apply for the new certificates.
† There are a bunch of rules, but, not relevant to this particular issue.
- ggm 5y agoIf you have the CSR. If you move CA or use the form of recruitment common in browsers the CSR often isn't to hand. Look I agree fundamentally, a Cert isn't a CSR. But it has the essential qualities, the critical components of the TBS which you needed to do the S part of the TB. TB | !TB is sometimes the question, in as much as policy is in the CSR, why they asked to be signed, what additional data flows including nonces and proofs of possession, what they asked for, distinct from what was signed over. But to validate the private keys use under a new CA? You don't need it. Should you? Well that's a policy question. If you were the original CA or RA you have reasonable confidence in why you need to do this and all the proofs you need regarding validity. Begs the question why you don't have the CSR, sure. If you aren't in the original certifying roles then gaining confidence in the cert you're resigning is pretty important and the costs here might be less than rekeying assuming a CSR isn't to hand.