OpenPGP: Add feature to map an email address (or a whole domain) to a specific key (accept address mismatch)
Categories
(MailNews Core :: Security: OpenPGP, enhancement)
Tracking
(Not tracked)
People
(Reporter: Thunderbird_Mail_DE, Assigned: KaiE)
References
Details
In Enigmail it was possible to select a (one) key for several different company mail addresses. This seems not to be possible with the integrated PGP feature in 78.* and would be a regression against Enigmail.
It is reported in German support forums:
|
Assignee | |
Comment 1•4 years ago
|
||
Yes, we don't support that currently.
We have a similar feature request in bug 1644085.
|
|
Assignee | |
Comment 2•4 years ago
|
||
Alex, in your scenario, do all employees own a copy of the secret key to decrypt those messages?
|
|
Assignee | |
Updated•4 years ago
|
|
||
Comment 3•4 years ago
|
||
Kai,
I enquired from the company referenced above regarding use of "company Keys" and they replied: "encrypted mails are decrypted on a separate system before they enter the user’s mailboxes. So there’s no key distribution needed on our side."
I´m having exactly the same issue. An option to manually select the public key that is used for encryption would do the job.
@Kai: Most companies decrypt the messages at a central gateway (which holds the public / private key pair) and then forward it internally to the desired recipient (the then decrypted message). This happens very often in the finance sector to comply with regulation. But it´s also an "easy" way to handle mail encryption without bothering the end user.
As far as I remember PGP keys can handle aliases but that would require you to renew / update your keys everytime someone joins / leaves your organization.
Anyway...I really need this feature too. Until then I have to revert to 68 :-/
(In reply to Kai Engert (:KaiE:) from comment #2)
Alex, in your scenario, do all employees own a copy of the secret key to decrypt those messages?
It is not necessary to share the secret key. You can have a list email address and an alias rule for gpg/pgp that assigns the key IDs of the list members to the list email address. Then emails to the list email address will be encrypted for all the members in this list. The disadvantage is, of course, everyone in the list has to manually maintain this alias rule. But in our scenario with ~10 members it is working very well.
|
|
Assignee | |
Updated•4 years ago
|
|
|
Assignee | |
Comment 6•4 years ago
|
||
See bug 1644085 comment 32, which suggests a solution that could also cover the scenario described in this bug.
|
||
Comment 7•4 years ago
|
||
I think alias rules (bug 1644085) has this covered.
Description
•