unable to import self-signed recipient encryption certificate
Categories
(MailNews Core :: Security: S/MIME, defect)
Tracking
(Not tracked)
People
(Reporter: hauser, Unassigned)
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36
Steps to reproduce:
http://kb.mozillazine.org/Installing_an_SMIME_certificate says to import such a certificate in the authorities tab and not "other people"
i) I tried to import the attached into Authorities
Actual results:
a) I got an error "This is nota certificate authority certificate, so it can't be imported into the certificate authority list"
Expected results:
- Say which attributes the recipient has to add to his certifcate and
- add a link to a help page that explains how to do that (e.g. with openssl, xca, https://github.com/kaikramer/keystore-explorer ...)
|
Reporter | |
Comment 1•5 years ago
|
||
It does work for recipient selfSig-cyLg@my-d.org (except that I cannot see it as per bug 956480 nor does import into "other people" do anything/not even an error), so
- IMHO the approach suggested in MozillaZine is fundamentally flawed since while I want to reach selfSig-cyLg@my-d.org in an encrypted way, I do not necessarily trust her/him to issue valid mail certificates for others!
see also Bug 1623568
|
||
Updated•5 years ago
|
|
||
Comment 2•5 years ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)
|
|
||
Comment 3•5 years ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)
|
|
||
Comment 4•5 years ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)
|
|
||
Comment 5•5 years ago
|
||
The severity of these bugs was changed, mistakenly, from normal to S3.
Because these bugs have a priority of --, indicating that they have not been previously triaged, these bugs should be changed to Severity of --.
|
||
Comment 6•4 years ago
•
|
||
Let's mark this wontfix. If you don't want to use certificate authorities, use OpenPGP instead of S/MIME.
|
|
||
Updated•2 years ago
|
Description
•