Windows 10 reached EOS (end of support) on October 14, 2025. For more information, see this article.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Where is generated private key stored during S/MIME CSR generation?

  • 1 cavab
  • 0 have this problem
  • 32 views
  • Last reply by const

more options

I generated a CSR file via the instructions at https://support.mozilla.org/en-US/kb/instructions-smime-certificate-using-csr#thunderbird:linux:tb145 . After submitting and receiving a certificate from a CA, importing it the People tab of the Certificate Manager does not do anything: nothing new appears in the Your Certificates tab.

Where are the private keys associated to the generated CSRs stored? How can I access them to resolve this?

Running 140.5.0esr via flatpak on Fedora 43 Kinoite.

I generated a CSR file via the instructions at https://support.mozilla.org/en-US/kb/instructions-smime-certificate-using-csr#thunderbird:linux:tb145 . After submitting and receiving a certificate from a CA, importing it the People tab of the Certificate Manager does not do anything: nothing new appears in the Your Certificates tab. Where are the private keys associated to the generated CSRs stored? How can I access them to resolve this? Running 140.5.0esr via flatpak on Fedora 43 Kinoite.

Chosen solution

Ok, so it appears this is may be a problem handling Sectigo's S/MIME certificate generation. It appears that if downloaded too quickly, Sectigo's initial file does not actually contain the key (checking with openssl x509). Downloading again, it did contain the key, though loading it required restarting Thunderbird before it eventually showed up.

Showing orphan private keys in the certificate manager (eg, the ones that show up with certutil -K) might make this process less stressful.

Read this answer in context 👍 0

All Replies (1)

more options

Seçilmiş Həll

Ok, so it appears this is may be a problem handling Sectigo's S/MIME certificate generation. It appears that if downloaded too quickly, Sectigo's initial file does not actually contain the key (checking with openssl x509). Downloading again, it did contain the key, though loading it required restarting Thunderbird before it eventually showed up.

Showing orphan private keys in the certificate manager (eg, the ones that show up with certutil -K) might make this process less stressful.

Sual ver

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.