<story><title>GnuPG 2.1.0 “modern” released</title><url>http://lists.gnupg.org/pipermail/gnupg-announce/2014q4/000358.html</url></story><parent_chain></parent_chain><comment><author>cryptbe</author><text>Congratulations Werner and GnuPG team!&lt;p&gt;&amp;gt; GnuPG now support Elliptic Curve keys for public key encryption. This is defined in RFC-6637. Because there is no other mainstream OpenPGP implementation yet available which supports ECC, the use of such keys is still very limited. [1]&lt;p&gt;Google End-To-End [2] supports ECC by default. We are working on supporting Ed25519, but encrypting and signing with NIST curves should work and be compatible with GnuPG. That said, we&amp;#x27;ve had a lot of compat issues, so it&amp;#x27;ll be great if Hacker News readers and GnuPG users can help test our implementation against GnuPG. You can generate keys in GnuPG and import them to End-To-End and vice versa, or you can encrypt&amp;#x2F;sign messages on one software and decrypt&amp;#x2F;verify them on the other. If you found a bug or anything that doesn&amp;#x27;t work as expected, you can report it at &lt;a href=&quot;https://code.google.com/p/end-to-end/wiki/Issues?tm=3&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;code.google.com&amp;#x2F;p&amp;#x2F;end-to-end&amp;#x2F;wiki&amp;#x2F;Issues?tm=3&lt;/a&gt;. If it&amp;#x27;s a security bug you&amp;#x27;re eligible for a monetary reward under our bug bounty program :-).&lt;p&gt;[1] &lt;a href=&quot;https://gnupg.org/faq/whats-new-in-2.1.html#ecc&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;gnupg.org&amp;#x2F;faq&amp;#x2F;whats-new-in-2.1.html#ecc&lt;/a&gt;
[2] &lt;a href=&quot;https://code.google.com/p/end-to-end/&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;code.google.com&amp;#x2F;p&amp;#x2F;end-to-end&amp;#x2F;&lt;/a&gt;</text></comment>
<story><title>GnuPG 2.1.0 “modern” released</title><url>http://lists.gnupg.org/pipermail/gnupg-announce/2014q4/000358.html</url></story><parent_chain></parent_chain><comment><author>JoshTriplett</author><text>One particularly nice feature of the new version: gpg-agent no longer just stores the passphrase and hands it out to gnupg.  Instead, gpg-agent actually holds the private keys and does crypto operations with them, and never lets any other process have the private keys or the passphrase (other than the pinentry program that prompts for the passphrase).&lt;p&gt;See &lt;a href=&quot;https://gnupg.org/faq/whats-new-in-2.1.html#nosecring&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;gnupg.org&amp;#x2F;faq&amp;#x2F;whats-new-in-2.1.html#nosecring&lt;/a&gt;</text></comment>