Home → Beta →

GnuPG version 2.1

• Edit

paul

10 Feb, 2015 02:35 PM

Aloha, Will GPG Tools eventually upgrade to use GnuPG 2.1

This is the current version with Beta 5 GPG Tools
gpg2 --version gpg (GnuPG/MacGPG2) 2.0.26
libgcrypt 1.6.2
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: ~/.gnupg
Supported algorithms:
Pubkey: RSA, RSA, RSA, ELG, DSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
CAMELLIA128, CAMELLIA192, CAMELLIA256 Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2

1. 1 Posted by Marcel on 12 Feb, 2015 03:16 PM

   

   The final Yosemite compatible version of the GPGSuite will NOT implement GnuPG 2.1 as far as I know, so this will come later ...

   I agree there are some nice new features in 2.1 (full list here: https://www.gnupg.org/faq/whats-new-in-2.1.html), but Elliptic Curve Cryptography (ECC) for example is still not completely standardized, quote:

   'For many people the NIST and also the Brainpool curves have an doubtful origin and thus the plan for GnuPG is to use Bernstein’s Curve 25519 as default. GnuPG 2.1.0 already comes with support for signing keys using the Ed25519 variant of this curve. This has not yet been standardized by the IETF (i.e. there is no RFC) but we won’t wait any longer and go ahead using the proposed format for this signing algorithm. The format for an encryption key has not yet been finalized and will be added to GnuPG in one of the next point releases. '

   • Edit

2. Support Staff 2 Posted by Steve on 13 Feb, 2015 03:28 PM

   

   Hi Paul,

   there are no immediate plans to adapt GnuPG 2.1 in GPG Suite. We are working on getting the Suite as stable as possible for the upcoming final release. So at the moment we are in a phase where no new features are worked on.

   We agree that there is a ton of improvements in 2.1 and can't wait to start taking benefit of those. But currently that is further down the road.

   All the best,
   steve

   • Edit

3. Support Staff 3 Posted by Steve on 01 Jun, 2015 02:36 PM

   

   We have a ticket for this problem. I connected this discussion with the existing ticket. That means, should this discussion get closed, it will be re-opened as soon as the ticket is closed. That way you'll receive a notification. Feel free to open a new discussions should you run into further problems or need assistance.

   • Edit

4. Steve closed this discussion on 01 Jun, 2015 02:36 PM.

5. Steve re-opened this discussion on 13 Jun, 2017 08:40 PM

6. Support Staff 4 Posted by Steve on 13 Jun, 2017 08:40 PM

   

   Hi Paul and Marcel,

   we have a first GPG Suite test build which integrates gpg 2.1. Here is the signature file for that release.

   It would be great if you could test this build and let us know if run into any trouble. Please note, that downgrading to the current beta release will require additional steps in case new keys were created using this test build. Depending on the test results, gpg 2.1 may soon land in the beta branch.

   All the best,
   steve

   • Edit

7. 5 Posted by paul on 14 Jun, 2017 10:09 PM

   

   validated signature- using terminal good signature
   validated signature using GPG Services GUI- had to quit Growl and Hardware Growler to enable the view

   Sent mail encrypted works fine so far.

   • signature.asc 834 Bytes
   • Edit

8. Support Staff 6 Posted by Steve on 15 Jun, 2017 10:03 AM

   

   Sounds good. Is Growl still maintained? Last blog post from them is from 2013.

   If any trouble arises, do let us know.

   Have a great day,
   steve

   • Edit

9. Steve closed this discussion on 15 Jun, 2017 10:03 AM.

10. paul re-opened this discussion on 16 Jun, 2017 09:50 PM

11. 7 Posted by paul on 16 Jun, 2017 09:50 PM

    

    Deleted Growl

    • signature.asc 834 Bytes
    • Edit

12. Support Staff 8 Posted by Steve on 18 Jun, 2017 05:11 PM

    

    Sounds reasonable. I think Apple has that functionality now covered nicely with notifications.

    I'm closing this discussion, which does not mean further feedback isn't welcome. You can re-open this discussion or just open a new one any time.

    Kind regards,
    steve

    • Edit

13. Steve closed this discussion on 18 Jun, 2017 05:11 PM.