Enabling the PGP plugin

  1. To check whether the PGP plugin is installed, check the Integrations tab in Zammad. This should show ‘PGP’ in the list of integrations. A green dot will appear next to its name if the plugin is enabled - here the plugin is not yet enabled:

Untitled

  1. To enable the plugin, open the settings for ‘PGP’, and toggle the switch in the top left corner of the page:

Untitled

Sending encrypted email to a user

  1. The ‘Public and Private Keys’ section will display all the known encryption keys and associated emails. To be able to send encrypted email to an email address, it is necessary to upload the public key associated with that email address. Usually the public keys will be sent from the PGP users themselves, as attachments to tickets created via email. Here’s an example of such a ticket:

Untitled

  1. To be able to reply to this user using encrypted email, download this attachment and upload it to the ‘Public and Private Keys’ section of the PGP integrations, by selecting ‘Add Public Key’, and then ‘Browse’:

Untitled

  1. The PGP key fingerprint and email will now show up in the list:

Untitled

  1. Replying on the ticket will now show the option to ‘Encrypt’, enabled by default. This means the reply will be sent encrypted. The padlock can be clicked to disable encryption.:

Untitled

Receiving encrypted email from a user:

  1. To receive encrypted email, a PGP key must be generated for the helpdesk email. For example, on Linux systems, this can be done using the gpg command, and filling in the name and email address for the new key. In this example, we create a key for ‘helpdesk’ with email address ‘[email protected]’:
gpg --gen-key                                                                                                                                                                                                                                                                                                                             ✔  8074  13:16:03
gpg (GnuPG) 2.2.27; Copyright (C) 2021 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.