GPG Suite heeft als doel om een eenvoudige installatie van GnuPG en aanverwante tools op het macOS-platform te bewerkstelligen. Met GnuPG kun je communicatiestromen en data beveiligen met encryptie en digitale handtekeningen. Het ondersteunt zowel OpenPGP als s/mime-standaarden. De ontwikkelaars van GPG Suite hebben versie 2018.4 uitgebracht, waarbij we moeten opmerken dat de macOS Mail-plug-in met de naam GPG Mail voortaan niet meer gratis wordt aangeboden en nu een licentie vereist na de probeerperiode van dertig dagen. Het is wel mogelijk om de andere onderdelen in de suite te gebruiken zonder licentie, door GPGMail te verwijderen. De aankondiging en aanpassingen van deze uitgave zien er als volgt uit:
GPG Suite 2018.4
Introducing GPG Mail 3 for macOS Mojave and High Sierra
macOS Mojave is just around the corner and we couldn't be more stoked about telling you, that GPG Mail is ready. For the best user experience, it is advised to install this release before upgrading to macOS Mojave. Otherwise you will have to manually enable GPG Mail after the upgrade.
For those of you who have been following us for a long time it might not come as much of a surprise, that after almost ten years of developing GPG Suite, we have decided to start charging a fee for continued use of GPG Mail. After the installation of this update you will be able to test GPG Mail for another 30 days. After the trial period is over, you will still be able to decrypt incoming messages, but in order to verify and encrypt new messages, a GPG Mail Support Plan is required. We hope you understand our decision and keep supporting us.
macOS 10.14 Mojave Support
Never have one of them pesky keys expire on you again
- GPG Mail 3 supports macOS 10.14 Mojave from day one. Enjoy secure communication on Apple's latest and greatest (remains to be seen) macOS.
GPG Mail 3.0
- GPG Keychain and GPG Mail will warn you four weeks before your key is about to expire. Never worry about expiring keys again, we've got you covered! Extending your key with one simple click has never been easier.
- Introduces proper support for PGP-Partitioned messages from PGP Desktop [#991]
GPG Mail 2.8 (Sierra only)
- Messages that went through MS exchange servers could trigger Mail to crash. This was - by far - our number one crasher and it is now a thing of the past [#977]
- Messages containing only encrypted attachments but not encrypted text were falsely displayed as partly encrypted [#986]
- In some cases, PGP/MIME encrypted and signed message recognized as partly encrypted did not show a signature [#987]
- PGP/MIME messages within a message/rfc822 mime part (inline) were not decrypted [#992]
- Re-added support for embedded filenames [#990]
- Inline PGP messages from Mailvelope were displayed as partly encrypted / partly signed [#989]
- A message's subject line could be manipulated to look like the message was signed when it was not. Credit for this finding goes to Hanno Böck (@hanno) [#1001]
GPG Keychain 1.4.5
- All fixes from GPG Mail 3 were back ported for version 2.8
- Inform users of keys about to expire and provide simple option to extend them [#59]
- New password strength indicator - color codes and smarter indicator for password strength [#442]
- Updated message during key generation [#455]
- In order to prevent users from leaking their secret key, if a key pair is exported, the secret key is always listed first. That makes it easier to catch that mistake [#452]
GPG Services 1.11.5
- During key creation, only active email addresses are suggested [#446]
- German umlaute were not properly encoded in key searches [#460]
- Remember status of "Sign", "Add to Recipients" and "Encrypt with Password" options [#128]
- When a message or file can not be decrypted due to a missing secret key, the error message now shows the key ID of the required key. That makes it much easier to understand why decryption would not work and to determine wether the correct key was used for encryption [#195]
- When a message or file can not be verified because the required public key does not exist, the error message now shows the key ID of the required key [#246]
- Updated to GnuPG 2.2.10 [#718]
- Using 127.0.0.1 in resolv.conf could prevent dirmngr from resolving the IP addresses of keyservers [#717]