Best Technology Stuff from Around the World

Software update: GPG Suite 2018.4

GPG Suite aims to provide a simple installation of GnuPG and related tools on the macOS platform. With GnuPG you can secure communication flows and data with encryption and digital signatures. It supports both OpenPGP and s / mime standards. The developers of GPG Suite have released version 2018.4, where we should note that the macOS Mail plug-in with the name GPG Mail is now no longer offered for free and now requires a license after the trial period of thirty days. It is possible to use the other parts in the suite without a license, by removing GPGMail . The announcement and adaptations of this edition are as follows:

GPG Suite 2018.4

Introducing GPG Mail 3 for macOS Mojave and High Sierra
macOS Mojave is just around the corner and we could not be more stoked about telling you, that GPG Mail is ready. For the best user experience, it is recommended to install this release before upgrading to macOS Mojave. Otherwise you will have to enable GPG Mail after the upgrade.
For those of you who have been following you for a long time you can not wait for that, that after almost 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

  • GPG Mail 3 supports macOS 10.14 Mojave from day one. Enjoy secure communication on Apple’s latest and greatest macOS.

Never have one of them pesky keys expire on you again

  • 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.

GPG Mail 3.0

Improvements

  • Introduces proper support for PGP-Partitioned messages from PGP Desktop [#991]

Fixes

  • 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 but not encrypted files were falsely displayed as partly encrypted [#986]
  • In some cases, PGP / MIME encrypted and signed message is not recognized as a signature [#987]
  • PGP / MIME messages within a message / rfc822 mime part (inline) were not decrypted [#992]
  • Supported for filenames [#990]
  • Inline PGP messages from Mailvelope were released 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 Mail 2.8 (Sierra only)

Fixes

  • All fixes from GPG Mail 3 were back ported for version 2.8

GPG Keychain 1.4.5

Improvements

  • New password strength indicator – color codes and smarter indicator for password strength [#59]
  • New password strength indicator – color codes and smarter indicator for password strength [#59]
  • 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]

Fixes

  • During key creation, only active email addresses are suggested [#446]
  • German umlaute were not properly encoded in key searches [#460]

GPG Services 1.11.5

Improvements

  • Remember status of “Sign”, “Add to Recipients” and “Encrypt with Password” options [#128]
  • When a message or file can not be decrypted, the key ID of the required key. That makes it much easier to understand why decryption would not work and that the correct key was used for encryption [#195]
  • . key ID of the required key [#246]

MacGPG 2.2.10

Improvements

  • Updated to GnuPG 2.2.10 [#718]

Fixes

  • Using 127.0.0.1 in resolv.conf could prevent dirng from resolving the IP addresses of keyservers [#717]
You might also like
Comments
Loading...