First Beta of GPGMail for macOS Sierra out now!
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
GPGMail for macOS 10.12 Sierra (Beta 1)
=======================================
A long year is coming to an end and we are all looking forward to some cosy and fun festivities to welcome the new year.
But before, we wanted to finally reward your patience. So after a painful and long waiting time, extensive reverse engineering and re-writing of major parts of our codebase, we are very happy to share the first beta of GPGMail for macOS Sierra with you.
Download:
https://releases.gpgtools.org/GPG_Suite-2016.12b1.dmg
SHA256: 2bb29067e7f2705a51b22f23080ca767bba4735ce16711a7d950e582737e8aaf
GPG Signature: https://releases.gpgtools.org/GPG_Suite-2016.12b1.dmg.sig
As with every beta we don't recommend using it in a production environment just yet, since bugs and crashes may occur.
Please report any bugs you find via System Preferences > GPGPreferences > Send Report.
We have added optional crash reporting to GPGMail in order for us to better understand when and where crashes are occuring.
We wish you the very best and happy festivities,
your GPGTools Team
=====
KNOWN ISSUES
* If multiple private keys are available for the same email address, GPGMail currently picks one at random to sign the message
* Some messages might not load correctly. If you can provide us with an example .eml file we'd love to debug the issue.
* If you cancel the pinentry request for signing upon sending a message it might lead to unexpected behavior
* Inline PGP is currently not supported at all, PGP/MIME will be used instead
* "BCC" recpients are currently not treated differently from "TO" or "CC" recipients (gnupg --hidden-recipients option not currently in use)
* The GPGMail Preferences layout is a bit wonky (Mail -> Preferences -> GPGMail)
* Keys that are imported using gnupg cli or GPG Keychain might require a restart of Mail in order to be picked up by GPGMail
* Mail rules for signed or encrypted messages will not work for PGP/MIME signed/encryted messages.
To receive further betas, make sure you are on the beta update channel. Open System Preferenes > GPGPreferences and in the Updates section check the option to 'Include beta builds'. Consider enabling auto-updates to ensure you receive notifications about further beta updates.
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJYZvcwAAoJEOimZEgNnkP1gUAP/2iwRpdg615JkjoAGYvgNF8U
/zoJArB4833mrKBMDO0nOJWB8jDh1fSpGY9GmNQFgnJZUtr7SXj7R0ruh1SzCTZ8
nruWPckxCNVVShWtK45u2m23sJy7P6vNfaBRfZPyKhMlGonxQ4HZB3Zh5LBt3eWx
p7sU5jugbNDcUs3QZs1fIMKEmun6bZ7PMN216T30/6vai8pV2t1N2+2OaEl/AWy3
NQTJ5s/BOSs3y2IkDN5NpUbudOfaDEwFQNyv53hORsPZ8vPmSTNRpESN4zzIuSYO
q4vCi2lRx1EBq0hI3TLyvWVS/Jp94tGpmhwwzShNChsEMANd//0UmSQ8cNqGYqFz
2O+L1j50fulHIjvlsAXtaGHRh8vJBR+oCe66Gb16Byey4pBwCKxKXb3SvYXvORkK
FGRSyH6863tYeFZZXB9ccDSjH9tVTOg/+nBxMOejCGXMJwJ24Ja6UFFBxL6ogpSw
GToqHrz/39ZvVzQSx2iV2F6h09xM/xuanBy7JF6FgmcOOxW5Dj7xqsnkF9MqH46y
j7JJPQkOpSqynv2387K8BZqd4memtiz0vy/b25qHMKiB/okbD8I/Vf+fIorp9a1F
cYD2ge6EVs4AtGmmYJ1zf9hHtg9fnUZd8PLMhGfDdPr+2pcGOiIPEh3rVAhbSQfK
ZPQs5/HY95RlTTswjMzi
=bKsb
-----END PGP SIGNATURE-----
We wish you a happy new year!
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by Bob on 31 Dec, 2016 03:37 AM
Thanks for the beta.
I'm already using ECC with curve266-19 keys.
Will you switch to GnuPG 2.1.x for the release version?
If not, when will you do so?
Regards!
2 Posted by Robert Vaessen on 31 Dec, 2016 05:46 PM
FYI - I've dowloaded and installed the beta on my Mac (running MacOS Sierra 10.12.2) with Mail.app Version 10.2 (3259). All seems to be working fine at the moment. I've only performed one test. Sent an 'encrypted' email from my private @vaessen.ws account to my @mac.com email account without any issues. Email was sent, received, decrypted and read without any problems noted.
I also verified the 'signing' capability. I signed a message using Mail.app, sent it from my private @vaessen.ws account to my @mac.com account without any issues. The email was signed, sent, received and read without any problems noted.
The 'Security' Check mark was present on the received message indicating a valid/unaltered message received from sender.
Thanks for getting us a beta that works! Signing and Encrypting our email should be the default. It should be easy. Thanks for making it easier! Thanks for all the hard work.
3 Posted by Zbigniew Krüger on 03 Jan, 2017 03:54 PM
There is an issue with signing emails. there is a popup window saying that the signature is not valid.
4 Posted by graham.mitchell on 04 Jan, 2017 09:49 AM
Weird issue downloading the beta dmg file: Safari repeatedly reports a 520 error, whilst the download proceeds fine using Firefox. Go figure.
5 Posted by Henrik Lied on 05 Jan, 2017 10:53 AM
I have a weird issue as well: With the latest beta, Mail.app is able to decrypt messages. But I am not able to either reply to emails (encrypted or not), and I'm not able to compose new messages. I've tried running the uninstaller several times to start fresh, but this isn't yielding any results either.
Ideas?
6 Posted by Lars Hilse on 09 Jan, 2017 03:51 PM
Downloaded, installed, works perfectly.
Thanks!
7 Posted by Lars Hilse on 10 Jan, 2017 02:51 PM
Came across "signature invalid". Checked, and doublechecked everything on this side.
Any ideas?
8 Posted by Zbigniew Krüger on 10 Jan, 2017 02:54 PM
I have the same issue with invalid signature. I tried to create new pair of keys and the problem is still there.
9 Posted by subgrad on 10 Jan, 2017 03:53 PM
SHA checksum mismatches with given SHA256: 2bb29067e7f2705a51b22f23080ca767bba4735ce16711a7d950e582737e8aaf.
Can anybody confirm this behavior?
10 Posted by Daiwei on 10 Jan, 2017 04:16 PM
Is there a changelog somewhere? Thanks!
11 Posted by Robert Vaessen on 10 Jan, 2017 11:09 PM
Depending on the email body, you may find that your email service provider has added some text to the body of the message. For example, when I send email to mailing lists, my mailman software adds a 'signature block' to the message, this causes the signature to come up as invalid because my original message (the one I sent) doesn't include the 'signature block' that's added by my mailman software. Some services, service providers and applications add tags, signature blocks, advertisement, etc to the body of the email that you send. If anything is added to the body of your email after you press 'send' it will cause the GPG Signature to be 'invalid'
You can examine the body of the message that was sent (check sent folder) with the body of the message as it was received (after it was relayed over the internet via various servers/services). It is possible that there was some 'modification' of the message. Even an extra line, space character, or 'virus checked' statement will cause the message to fail validation.
12 Posted by graham.mitchell on 11 Jan, 2017 11:05 AM
This comment was split into a new discussion: Signature invalid
The invalid signature error is appearing - in my case - for all sent messages. It may be (I'm testing using an Apple provided mac.com account) that the body of the message is being altered by Apple as soon as it hits their server, and it may be that I'm viewing that sent message as it exists on their server rather than on my local machine (I'm not sure how to check that). However, if that is the case, the error message that I'm seeing is confusing as it suggests to me that my signature is broken in some way, where there's nothing wrong with the signature as applied to the message, rather that the message has been altered post-signing. Perhaps the warning message should/could state this?
13 Posted by Fortran on 13 Jan, 2017 11:01 AM
I can confirm. SHA checksum mismatches with given SHA256.
14 Posted by Russell Fulton on 13 Jan, 2017 09:10 PM
I have been using GPGMail beta since it was release with out problems. I am a light user and it is mostly just checking signature.
Support Staff 15 Posted by Luke Le on 13 Jan, 2017 09:20 PM
@Fortran: what Shasum are you seeing? Additional check: gpg --verify GPG_Suite-2016.12b1.dmg.sig
@All: we're currently investigating the false verification results. It looks like a bug in Apple Mail, since S/MIME messages are affected as well under certain circumstances. Hope to find a solution for b2
16 Posted by subgrad on 13 Jan, 2017 09:24 PM
I got as checksum 7aaab21a20d951cc94e3bd854747272d6bb7ff93
17 Posted by Fortran on 13 Jan, 2017 09:29 PM
Thanks. It works. I've got the right checksum now. puhh :)
18 Posted by subgrad on 13 Jan, 2017 09:36 PM
Sorry, sha256 is correct. I will start testing.
19 Posted by Bob on 14 Jan, 2017 01:03 AM
Actually Apple Mail is a piece of junk since after Snow Leopard. I'm filing bug reports to Apple since years and they are not fixing any single one of them.
20 Posted by Peter on 18 Jan, 2017 08:55 AM
The beta isn't available anymore:
"Service Temporarily Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later."
And on the home page (gpgtools.org), I can read, "(GPGMail support for macOS Sierra coming soon)".
When will there be a next beta (or a final release)? How soon is "soon"?
Support Staff 21 Posted by Luke Le on 18 Jan, 2017 08:56 AM
We've experienced a short timeout of one of the download servers. Should be back up.
22 Posted by Peter on 18 Jan, 2017 10:27 AM
Works, thanks!
Support Staff 23 Posted by Steve on 24 Feb, 2017 12:27 PM
2017.1b2 is now on the homepage.
Steve closed this discussion on 24 Feb, 2017 12:27 PM.
Robert W. Glatzl re-opened this discussion on 24 Feb, 2017 02:11 PM
24 Posted by Robert W. Glatz... on 24 Feb, 2017 02:11 PM
Hi Steve!
why did I receive this today?
And on the homepage is truly 2017.1b2, still the same version (I checked the SHA) which is available since Jan 23, 2017.
--
Robert W. Glatzl
[email blocked]
Support Staff 25 Posted by Steve on 24 Feb, 2017 03:19 PM
Robert, you receive the message because I updated the discussion you are subscribed to and I closed that discussion, which you now re-opened with your response.
I suggest to move forward new discussions should be created for any additional questions.
Yes 2017.1b2 is the same version. The homepage lists January 23rd, 2017 as release date.
All the best,
steve
Steve closed this discussion on 24 Feb, 2017 03:19 PM.