PGP key update for existing keys

Feature requests
1

Title: PGP key update without deleting and re-adding

  1. I noticed when trying to update existing PGP keys, Zammad displays the message “Fingerprint There is already a PGP key with the same fingerprint.” - which means the existing key needs to be deleted and then the updated key re-uploaded.
  2. PGP key management
  3. lacking functionality
  4. The expectation is that an updated key with the same fingerprint (e.g. expiry date update or revocation) can be updated directly, despite a key with the same fingerprint exists in the directory, - and then is processed accordingly.

Thank you :folded_hands:t2:

2

one additional feature I just noticed is, - when an inbound encrypted e-mail is sent to Zammad, including the public-key as attachment, Zammad seems not to process/import the attached key automatically, - which I would expect from a user experience perspective. tofu - trust on first usage.

zammad missing key
zammad missing key662×232 11.8 KB

3

You might not want to put several feature requests into one thread and might want to use the template. Also, the latter one definitely is a duplicate. Use the search function.