It is sometimes useful to have a long-term storage key and a feature in the MUA
to add an additional public key encrypted packet to a message which was
encrypted to a temporary key.
Description
Description
Revisions and Commits
Revisions and Commits
| rG GnuPG | |||
| rG600df5259db0 gpg: Detect duplicate keys with --add-recipients. | |||
| rGd528d0b06533 gpg: New commands --add-recipients and --change-recipients. | |||
| rG1695cf267edf gpg: New option --show-only-session-key | |||
| rM GPGME | |||
| rMcd79fc39736f core: New encryption flags GPGME_ENCRYPT_ADD_RECP and _CHG_RECP. | |||
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Resolved | timegrid | T1825 Add a re-encrypt to additional key | ||
| Open | None | T8016 Keep symmetric encryption keys with --add-recipients |
Event Timeline
Comment Actions
I now see I misunderstood the problem description.
The point is that a user has a message that is encrypted to key X. After
receiving the message, he wants to allow another key (say Y) to decrypt the
message by adding a symmetrically encrypted data packet to the message for Y,
i.e., without reencrypting the whole thing.
Comment Actions
Looks good to me on gpg4win-5.0.0-beta479 @ win11:
- gpg --show-only-session-key --decrypt FILE shows only the session key
- gpg --add-recipients -r UID1 FILE adds recipients (tested with one or more uids)
- gpg --change-recipients -r UID FILE changes the recipients (tested with one or more uids)
Comment Actions
Regarding my comment T1825#191055 : The mane page has long been updated and gpgme support is also available. For the symmetric session key, see the feature request T8016