Will not work on macOSX Sierra
Note from GPGTools, December 30
Hi all,
yesterday, December 29th, we have sent an email to all of the
watchers in this discussion.
Unfortunately we couldn't simply use our support platform to notify
all watchers, since we were told that if the number of watchers
exceeds a certain amount, no more email notifications will be
sent.
Once we have received some feedback from our users, we will release
the beta on our website and also through our beta update
channel.
To clarify some things mentioned in this discussion:
-
Crash reporting is optional. You will be asked if you want to opt-in the first time GPGMail discovers a crash.
-
The reports certainly do not include any keys (neither secret nor public). They are standard macOS crash reports and you can find them under ~/Library/Logs/DiagnosticReports/ to see what they look like
For those who just recently subscribed to the discussion, the email from yesterday is reproduced in full below.
Hope you all have a good start into the new year. Enjoy your celebrations!
<3 and ☀
GPGTools
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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-----
iQIcBAEBAgAGBQJYZpW7AAoJEOimZEgNnkP1HHIP+wVHNmbR7C5bT6MH0QYK3wwL
l2BoRVRsp81aAQNdZ8U81F0+ecxtVtk/xmlzCB+k5pdCpWwBE9P/vZSjjsiYgCJy
dIozrkWLZVrF1n5YgSBJlqZlZiwK6+xgX9Wg4x16I33j6VEvMoTcc/FhNXI0aTni
az0mEp4Imi4yCPvMELP8FSsspF3kIOxRiluClvQStoJk+N3cQZEIFNI6CPTsIJ6s
4Nl5iMhQzmya6P/HwLQBS5JiCTfXlvTSRUoCe6mt7smAX2+lCq/ODXOLxoXfYT4y
pAiKHZDSxMObMegGJlNAeweed01E/0jzpD/sAV3msk6NJcoOwi4Jtx7cArVn5tKw
imtEQQyJF5nPpVw5zGC+vxNKtzTBd7Ol8o2ZbUMTWNmCNRWdgxyUAncrYSjnmE3A
K0VGB3MO4Q0bFw8KYJ3xoLM058HnrllWCzRsje+gdSfGI0H0UCbGnA75TVapRg+i
3iKCMwMtTgqx37alBmwFZ6NmXCFch9uRJZAWZqCHndhpUrQtmkRcNHX7abdErLAd
U+imrXSBN+rb/9GJiODHbzESvE4K7SIFp5Z5ARH8e0Pm9yHDhYruGBLv+WnVdfVp
Eh9SQ2iVPKkWS/TTUzHrfNomF6hV2Uqj+GLIChS1L+v/duBYr6O13r846Ya908pX
xTWCtFU9Px/B0jx4/+AR
=vGSV
-----END PGP SIGNATURE-----
Original first post was:
The entire suit will not work on macOSX Sierra. Hope you have went
throught your way from Yosemite to El Capitain to Sierra.
Good Luck
Showing page 57 out of 60. View the first page
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
1681 Posted by halves on 30 Dec, 2016 10:16 AM
I´m very interesting for running GPG Mail in Sierra, so please add me to your notification list. Thank you for your great work!
1682 Posted by tokke on 30 Dec, 2016 02:43 PM
I am also very interested :)
1683 Posted by Shad Sterling on 30 Dec, 2016 02:49 PM
+1
1684 Posted by Jerald on 30 Dec, 2016 04:47 PM
Any progress on this? We're coming up on several months since Sierra and a couple months since your notice. How can we help?
1685 Posted by Ted on 30 Dec, 2016 04:50 PM
+1
Support Staff 1686 Posted by Luke Le on 30 Dec, 2016 05:17 PM
Hi all,
yesterday, December 29th, we have sent an email to all of the watchers in this discussion.
Unfortunately we couldn't simply use our support platform to notify all watchers, since we were told that if the number of watchers exceeds a certain amount, no more email notifications will be sent.
Once we have received some feedback from our users, we will release the beta on our website and also through our beta update channel.
To clarify some things mentioned in this discussion:
Crash reporting is optional. You will be asked if you want to opt-in the first time GPGMail discovers a crash.
The reports certainly do not include any keys (neither secret nor public). They are standard macOS crash reports and you can find them under ~/Library/Logs/DiagnosticReports/ to see what they look like
For those who just recently subscribed to the discussion, the email from yesterday is reproduced in full below.
Hope you all have a good start into the new year. Enjoy your celebrations!
<3 and ☀
GPGTools
1687 Posted by Dimitry Andric on 30 Dec, 2016 07:56 PM
Luke, would it be too crazy to attempt to install this on El Capitan, just to see if it works? Would that give any useful feedback? (I'm not ready to migrate to Sierra at this point.)
Support Staff 1688 Posted by Luke Le on 30 Dec, 2016 08:04 PM
Hi Dimitry,
this version of GPGMail won't run on El Capitan. We've touched too many of our entry points and a lot are not available on El Capitan or worked differently.
Is there any reason why you would want to do that? Our current stable version of GPGMail should run fine on El Capitan.
1689 Posted by wteiken on 30 Dec, 2016 11:51 PM
Please add me to the notification list.
1690 Posted by Bob on 31 Dec, 2016 03:48 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!
1691 Posted by Austin Burbridg... on 01 Jan, 2017 01:00 AM
Please add me to the notification list.
Thanks!
1692 Posted by Aaron on 01 Jan, 2017 03:12 AM
This comment was split into a new discussion: how to verify sha256 checksum?
Not sure how to verify a "SHA256" checksum.. Can anyone help?
I understood how to verify the SHA1 checksum for the previous "GPG Suite 2016.10" file, by following the instructions on the GPGTools Support site at: https://gpgtools.tenderapp.com/kb/how-to/how-to-verify-the-download...
I just used the "shasum" command on Terminal and compared the SHA1 checksums. But how do I do this with a "SHA256" checksum?
Thank you very much for any help!
1693 Posted by gpgtools on 01 Jan, 2017 11:50 AM
+1
1694 Posted by Dante Profeta on 01 Jan, 2017 04:19 PM
Thank you for your efforts.
Please add me too to the notification list.
1695 Posted by Greg on 01 Jan, 2017 07:45 PM
Appreciate your work on this!
Anxiously waiting for Sierra compatibility!
Thanks,
g/m
1696 Posted by Olev on 01 Jan, 2017 08:20 PM
Please add me to your list thanks!
1697 Posted by Mike S on 01 Jan, 2017 08:45 PM
Please include me in the discussion thread and updates.
Thanks.
1698 Posted by David Bruce Leo... on 02 Jan, 2017 08:07 PM
Please add me to your notification list.
1699 Posted by Nik Hemmeryckx on 02 Jan, 2017 10:59 PM
Check. (BTW The sky really is grey, today.)
1700 Posted by Fabrice B on 02 Jan, 2017 11:39 PM
Thanks to add me to your notification list.
1701 Posted by Ryan Clark on 03 Jan, 2017 07:52 AM
Please add me to the list.
1702 Posted by Fabio Ruini on 03 Jan, 2017 10:49 AM
Eagerly looking forward! :)
1703 Posted by davidcwest on 03 Jan, 2017 01:03 PM
Anyone else having problems downloading? get a 503
Edit: It is back now
1704 Posted by ksnider on 03 Jan, 2017 02:03 PM
So, the biggest problem I'm seeing is the inability to load several messages - the same ones each time - most of these appear to be mailing list messages, as opposed to the issue mentioned in the known issues (messages with multiple keys).
I haven't been able to track down a specific pattern yet on which messages will load or fail to load, but it's the same messages each time.
1705 Posted by Jorge Gomes on 04 Jan, 2017 09:10 AM
Testing it.
1706 Posted by Cai on 04 Jan, 2017 11:23 AM
Thank you so much for this beta!!
Brief testing shows no issues for me. If I encounter any I'll report through the requested feedback channel.
Thanks again for all the work you've put in, this is absolutely essential software. You should charge for it.
1707 Posted by stevie on 04 Jan, 2017 11:24 PM
Looking forward to be able to update my mac
1708 Posted by Chris on 05 Jan, 2017 01:30 PM
Beta installs cleanly, able to sign messages outgoing however when I view the messages in my Sent mailbox, they all read as having an invalid signature. If I send a signed message to myself to check, the signature in the sent box reads as invalid, however looking at the same message in my inbox reads as a valid signature. The first three attached screenshots are when viewing the sent item, and the fourth is looking in the inbox.
If I send myself a signed + encrypted message, both the signature and encryption show as valid in the sent item, and the decrypted message displays properly. So this seems to solely be an issue with signature validation with respect to signed sent items, and not encrypted sent items. The last attached screenshot is viewing an encrypted message from my sent items.
1709 Posted by Kazansky on 05 Jan, 2017 01:54 PM
Waiting for an update. Download not working (503 error code).
Cheers,
Kazansky
1710 Posted by dan on 05 Jan, 2017 02:51 PM
Watching!
Thanks for your effort. This is much appreciated.
d