sr2/cloud.sr2.uk
6
0
Fork 1
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

Update file names for images in the imported posts

Browse source
This commit is contained in:
Ana Custura 2026-05-11 12:03:05 +01:00
parent 1fddcd2d4f
commit b765db9052
25 changed files with 22 additions and 22 deletions
Download patch file Download diff file Expand all files Collapse all files

18
docs/link/pgp.md
View file

@ -9,29 +9,29 @@ sidebar_position: 100
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](/docs/link/admin/pgp/Untitled.png)
![integrations](/docs/link/admin/pgp/integrations.png)
1. To enable the plugin, open the settings for ‘PGP’, and toggle the switch in the top left corner of the page:
![Untitled](/docs/link/admin/pgp/Untitled1.png)
![pgp_integration](/docs/link/admin/pgp/pgp_integration.png)
## 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](/docs/link/admin/pgp/Untitled2.png)
![example_public_key](/docs/link/admin/pgp/example_public_key.png)
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](/docs/link/admin/pgp/Untitled3.png)
![add_public_key](/docs/link/admin/pgp/add_public_key.png)
1. The PGP key fingerprint and email will now show up in the list:
![Untitled](/docs/link/admin/pgp/Untitled4.png)
![public_key_list](/docs/link/admin/pgp/public_key_list.png)
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](/docs/link/admin/pgp/Untitled5.png)
![encrypt_replies](/docs/link/admin/pgp/encrypt_replies.png)
## Receiving encrypted email from a user:
@ -81,15 +81,15 @@ gpg --export-secret-key -a helpdesk > helpdesk.priv
1. The next step is to upload the helpdesk’s public and private keys to Zammad. The private key will be used to decrypt messages that were sent encrypted to the helpdesk. The public key will be distributed to the helpdesk users who wish to send encrypted email. First, upload the public key to the ‘Public and Private Keys’ section of the PGP integrations, by selecting ‘Add Public Key’, and then ‘Browse’ and selecting the public key exported in the previous step:
![Untitled](/docs/link/admin/pgp/Untitled6.png)
![import_helpdesk_public_key](/docs/link/admin/pgp/import_helpdesk_public_key.png)
1. Now add the private key, by selecting ‘Add Private Key’, and then ‘Browse’ and selecting the private key exported in the previous step:
![Untitled](/docs/link/admin/pgp/Untitled7.png)
![import_helpdesk_priv_key](/docs/link/admin/pgp/import_helpdesk_priv_key.png)
The display should now indicate the private key was uploaded
![Untitled](/docs/link/admin/pgp/Untitled8.png)
![show_imported_keys](/docs/link/admin/pgp/show_imported_keys.png)
1. Ticket replies will now be sent signed by default. When an encrypted email is sent by a user, its contents will automatically be decrypted and displayed in a ticket.