You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi. First of all, thank you for this package it's really great.
This is surely most me missing something than an issue but, here it is. I'm generating a self signed CA (with basicConstraints cA flag to true, issuer as itself and signed with its own private key) that I convert to PEM and write it down to a file before storing it into CA windows store with certmgr. Then, I create another certificate with my previous CA's subject attributes as issuer and sign it with my CA's private key. I convert it to PEM and write it down to a file, do the same with the private key, but when I use them with a server app (apache, npm serve) chrome (and other browsers) give me a ERR_SSL_SERVER_CERT_BAD_FORMAT. And as soon as I remove the line that set issuer's attributes, browsers consider certificate as a risk but I can reach my served files.
I did the same logic with openssl and it worked.
What am I missing ?
The text was updated successfully, but these errors were encountered:
Hi. First of all, thank you for this package it's really great.
This is surely most me missing something than an issue but, here it is. I'm generating a self signed CA (with basicConstraints
cA
flag totrue
, issuer as itself and signed with its own private key) that I convert to PEM and write it down to a file before storing it into CA windows store withcertmgr
. Then, I create another certificate with my previous CA's subject attributes as issuer and sign it with my CA's private key. I convert it to PEM and write it down to a file, do the same with the private key, but when I use them with a server app (apache, npm serve) chrome (and other browsers) give me aERR_SSL_SERVER_CERT_BAD_FORMAT
. And as soon as I remove the line that set issuer's attributes, browsers consider certificate as a risk but I can reach my served files.I did the same logic with openssl and it worked.
What am I missing ?
The text was updated successfully, but these errors were encountered: