cross signing certificates during offline root's renewal (what do I do with them?)
i know below scenario seems if i'm looking validation moving sha1 sha512/256, asking cross singing certificates that generated during offline root ca's renewal. thanks!
i have 2 tier pki single offline root , single subordinate issuing ca. both cas have sha1 certificates. i need root ca sha512 , issuing ca sha512. both cas use http cdps exclusively (no ldap cdps). below i’ve done far accomplish along few questions. question (also below) is what do cross signing certificates issued during root's renewal.
root ca
1. change sha512
>certutil -setreg ca\csp\cnghashalgorithm sha512
2. restart ca service
3. renew cert via gui new key pair
4. copy following files cdp , aia locations
>c:\windows\system32\certsrv\certenroll\ca01_ps inc. root ca(1).crt
>c:\windows\system32\certsrv\certenroll\ps inc. root ca(1).crl
5. publish new root ca ad
>certutil -dspublish -f "ca01_ps inc. root ca(1).crt" rootca
6. update local trusted roots , verify pkiview
>certutil -pulse
>ca container in pkiview shows renewed root status of ok!
question: do cross signing certificates issued well? toss them in aia locations , publish them ad well. if so, correct certutil syntax publishign them (e.g. rootcax0 & rootcax1)?
>c:\windows\system32\certsrv\certenroll\ca01_ps inc. root ca(1-0).crt
>c:\windows\system32\certsrv\certenroll\ca01_ps inc. root ca(0-1).crt
issuing ca
1. change sha256>certutil -setreg ca\csp\cnghashalgorithm sha256
2. generate request, move root, approve , bring issuing ca
3. new cert automatically published ad since issuing ca domain joined
4. manually move "c:\windows\system32\certsrv\certenroll\ca02.ad.ps.com_ps inc. subordinate ca i(1).crt" aia location.
5. verify new crl has been published cdp location
6. question: else i'm missing?
1) crossca certificates.
certutil -dspublish -f ca01_ps inc. root ca(1-0).crt crossca
certutil -dspublish -f ca01_ps inc. root ca(0-1).crt crossca
they show in pkiview.msc on aia tab cross ca certificates.
also, copy them web publication point.
2) issuing ca, missed restarting adcs after setting sha512 registry entry.
brian
Windows Server > Security
Comments
Post a Comment