<?xml version="1.0" encoding="iso-8859-1" ?>
<?xml-stylesheet title="XSL_formatting" type="text/xsl" href="/images/lists/rssstyle2.xsl"?>
<rss version="2.0">
<channel>
<title>GnuPG | devel</title>
<description>Mailing List Archive by Gossamer Threads</description>
<link>http://www.gossamer-threads.com/lists/gnupg/devel/</link>
<language>en-us</language>
<copyright>(c) Gossamer Threads Inc. All rights reserved.</copyright>
<lastBuildDate>24 May  2013 11:44:31 -0800</lastBuildDate>
<ttl>120</ttl>
<image>
<title>Gossamer Threads | GnuPG | devel</title>
<width>75</width>
<height>23</height>
<link>http://www.gossamer-threads.com/lists/gnupg/devel/</link>
<url>http://www.gossamer-threads.com/images/lists/rss_logo.jpg</url>
</image>
<item>
<title>distinguishing public from secret keys with gpgme</title>
<description>Hey all, Using gpgme 1.4.1, I&amp;#039;m trying to pick out which keys in the keyring have the secret component, and can be used for signing and decryption.</description>
<pubDate>24 May  2013 09:04:52 -0800</pubDate>
<link>http://www.gossamer-threads.com/lists/gnupg/devel/61482</link>
</item><item>
<title>2.1 key migration</title>
<description>Hi! I just pushed this change for GnuPG 2.1 (i.e. git master):   Implement unattended OpenPGP secret key import.     With the gpg-agent takin</description>
<pubDate>22 May  2013 02:24:09 -0800</pubDate>
<link>http://www.gossamer-threads.com/lists/gnupg/devel/61423</link>
</item><item>
<title>[PATCH] Allow the user to specify AES256 as well as AES128.</title>
<description>--- agent/agent.h   |  4 +++ agent/gpg-agent.c |  6 +++- agent/protect.c  | 104 +++++++++++++++++++++++++++++++++++++----------------- 3 file</description>
<pubDate>21 May  2013 10:34:00 -0800</pubDate>
<link>http://www.gossamer-threads.com/lists/gnupg/devel/61415</link>
</item><item>
<title>[Announce] GnuPg 2.0.20 released</title>
<description>Hello! We are pleased to announce the availability of a new stable GnuPG-2 release: Version 2.0.20. The GNU Privacy Guard (GnuPG) is GNU&amp;#039;s tool for</description>
<pubDate>10 May  2013 09:37:08 -0800</pubDate>
<link>http://www.gossamer-threads.com/lists/gnupg/devel/61364</link>
</item><item>
<title>Change to generate compliant keys for compact representation.</title>
<description>Greetings. I updated cipher/ecc.c in libgcrypt so that GnuPG generates only compliant keys that would allow the easiest compact representation, acco</description>
<pubDate>09 May  2013 15:00:01 -0800</pubDate>
<link>http://www.gossamer-threads.com/lists/gnupg/devel/61358</link>
</item><item>
<title>GnuPG Command line: now in the Play Store!</title>
<description>https://play.google.com/store/apps/details?id=info.guardianproject.gpg This alpha release of our command-line developer tool brings GnuPG to Android</description>
<pubDate>09 May  2013 07:27:48 -0800</pubDate>
<link>http://www.gossamer-threads.com/lists/gnupg/devel/61348</link>
</item><item>
<title>How to disable gnome-keyring (was: How to test my build of gpg2?)</title>
<description>On 2013-05-08 at 17:33 -0700, Andrey Jivsov wrote: &amp;gt; I am getting the error: &amp;gt; &amp;gt; gpg: agent_genkey failed: Unsupported certificate &amp;gt; &amp;gt; Key generation</description>
<pubDate>08 May  2013 18:55:45 -0800</pubDate>
<link>http://www.gossamer-threads.com/lists/gnupg/devel/61346</link>
</item><item>
<title>How to test my build of gpg2?</title>
<description>I wonder what&amp;#039;s the process of running my own build of gpg2? I am getting the error: &amp;gt; gpg: agent_genkey failed: Unsupported certificate &amp;gt; Key genera</description>
<pubDate>08 May  2013 17:33:40 -0800</pubDate>
<link>http://www.gossamer-threads.com/lists/gnupg/devel/61345</link>
</item><item>
<title>using alternate sources of entropy</title>
<description>Hi, For various reasons we&amp;#039;re exploring alternatives to /dev/random on Android. Primarily because it doesn&amp;#039;t fill fast enough, and we do not have roo</description>
<pubDate>07 May  2013 09:19:02 -0800</pubDate>
<link>http://www.gossamer-threads.com/lists/gnupg/devel/61333</link>
</item><item>
<title>[PATCH] UTF8 Filenames under Windows</title>
<description>As GnuPG’s command line does not support UTF 16 filenames, all filenames must be encoded in UTF8. With Linux this just works fine, but the Windows A</description>
<pubDate>05 May  2013 09:17:05 -0800</pubDate>
<link>http://www.gossamer-threads.com/lists/gnupg/devel/61318</link>
</item>
</channel>
</rss>
