1
24.1 Legacy Series / Re: Download Complete certificate chain for Intermediate CA
« on: April 04, 2024, 11:44:47 pm »
I apologize on the previous post, since I did make some mistakes. I was looking into the permutations on what seems to be the behaviour. You replied while I was making corrections to the previous post. Anyways, I had followed the steps you outlined. I used secp384 r1 and sha 256 throughout with 365 days validity. I did add a common name for my final certificate.
The only difference being I used the local machine store rather than the user store to for the certificates. I am viewing the certificate directly in windows rather than using the browser and installing it on the router web interface,but I don't think these should make any difference.UPDATE: It does make a difference especially with pfsense certs.
I did notice some differences between the certs I created in both pfsense and opnsense GUIs and hence the whole reason for my OP
@netnut With your clarifications, I do have an understanding of what's going on. I don't understand the real reason behind these differences but it seems to be so. I am newbie in understanding certificate implementation. I studied these back in college and that was a long time ago.
The only difference being I used the local machine store rather than the user store to for the certificates. I am viewing the certificate directly in windows rather than using the browser and installing it on the router web interface,
I did notice some differences between the certs I created in both pfsense and opnsense GUIs and hence the whole reason for my OP
- For Pfsense certs, I imported the root cert in the Windows local machine store in root certificates section.
I found out that the final certificate does not validate without importing the intermediate CA as well.
UPDATE: Google chrome does validate against the root certificate but windows certificate viewer does not validate the server cert against the root certificate. It requires the Intermediate certificate to be installed in the certificate store.
Additionally, if I let automatically let windows choose, it installs the root certificate in the intermediate certificates store, I don't know why thats so. - I followed same steps with opnsense. The opnsense cert validates itself with the root certificate installed. The intermediate certificate never shows itself as a part of the certificate chain, even if I install the intermediate certificate.
Update: Google Chrome shows the whole certificate chain as you said, but weirdly windows certificate viewer does not
@netnut With your clarifications, I do have an understanding of what's going on. I don't understand the real reason behind these differences but it seems to be so. I am newbie in understanding certificate implementation. I studied these back in college and that was a long time ago.