<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.encryption.gpg.devel">
    <title>gmane.comp.encryption.gpg.devel</title>
    <link>http://blog.gmane.org/gmane.comp.encryption.gpg.devel</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16909"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16902"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16901"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16896"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16893"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16892"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16891"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16888"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16887"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16880"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16873"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16861"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16860"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16857"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16854"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16847"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16841"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16836"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16828"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16826"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16909">
    <title>Python bindings for GnuPG</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16909</link>
    <description>&lt;pre&gt;For those of you seeking to use GnuPG from Python, there is an overview at

  http://wiki.python.org/moin/GnuPrivacyGuard

I've just overhauled it.
My recommendation currently is to use James Henstridge's PyGPGME.
As it is actively maintained and even supports Python 3 and 2 since March.

An interesting approach is W. Trevor King's pgp-mime which uses pyassuan 
to speak to gpgme-tool. Haven't tried it. 

Happy Hacking,
Bernhard
&lt;/pre&gt;</description>
    <dc:creator>Bernhard Reiter</dc:creator>
    <dc:date>2012-05-11T21:17:57</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16902">
    <title>npth-0.90 build report</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16902</link>
    <description>&lt;pre&gt;This morning, I successfully built npth-0.90 on about 80% of the 25 or
so flavors of Unix in our test lab.  There were, however, some
glitches that I could overcome, some machines on which a successful
build has not been possible, and one machine on which the build
succeeds, but the test fails.

When I attempted manual rebuilds after automated procedures failed,
I set PATH to a minimal list, such as /bin:/usr/bin.

Here is a summary of problems:

------------------------------------------------------------------------

Solaris 10 (SPARC, x86, x86_64) and 11 (x86_64):

Undefinedfirst referenced
 symbol      in file
accept                              ../src/.libs/libnpth.so
recvmsg                             ../src/.libs/libnpth.so
sendmsg                             ../src/.libs/libnpth.so
connect                             ../src/.libs/libnpth.so

    Need LIBS=-lsocket to resolve symbols.  With that addition,
    the build completes and the tests pass.

---------------------------------------&lt;/pre&gt;</description>
    <dc:creator>Nelson H. F. Beebe</dc:creator>
    <dc:date>2012-05-08T14:07:01</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16901">
    <title>[Announce] nPth - The New GNU Portable Threads Library</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16901</link>
    <description>&lt;pre&gt;Hi!

We are pleased to announce the first tarball release of the
New GNU Portable Threads Library: nPth version 0.90.

nPth is a non-preemptive threads implementation using an API very similar
to the one known from GNU Pth.  It has been designed as a replacement of
GNU Pth for non-ancient operating systems.  In contrast to GNU Pth is is
based on the system's standard threads implementation.  Thus nPth allows
the use of libraries which are not compatible to GNU Pth.

GNU Pth is often used to provide a co-routine based framework.  GnuPG-2
makes heavy use of this concept for good audibility, general security
concerns, and ease of implementation.  However, GNU Pth has the drawback
that ugly hacks are required to work with libraries which are not GNU
Pth aware.

The nPth tarball and its signature are available as

  ftp://ftp.gnupg.org/gcrypt/npth/npth-0.90.tar.bz2
  ftp://ftp.gnupg.org/gcrypt/npth/npth-0.90.tar.bz2.sig

and at all GnuPG mirrors.  See the included README file and the npth.h
header for documentati&lt;/pre&gt;</description>
    <dc:creator>Werner Koch</dc:creator>
    <dc:date>2012-05-08T10:39:49</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16896">
    <title>[PATCH] sm/certreqgen-ui.c</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16896</link>
    <description>&lt;pre&gt;Hello, 

While trying to use gpgsm --gen-key, I found two mistakes.

diff --git a/sm/certreqgen-ui.c b/sm/certreqgen-ui.c
index 236d53b..41492f5 100644
--- a/sm/certreqgen-ui.c
+++ b/sm/certreqgen-ui.c
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -339,12 +339,12 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; gpgsm_gencertreq_tty (ctrl_t ctrl, estream_t output_stream)
   /* DNS names.  */
   tty_printf (_("Enter DNS names"));
   tty_printf (_(" (optional; end with an empty line):\n"));
-  ask_mb_lines (&amp;amp;mb_email, "Name-DNS: ");
+  ask_mb_lines (&amp;amp;mb_dns, "Name-DNS: ");
 
   /* URIs.  */
   tty_printf (_("Enter URIs"));
   tty_printf (_(" (optional; end with an empty line):\n"));
-  ask_mb_lines (&amp;amp;mb_email, "Name-URI: ");
+  ask_mb_lines (&amp;amp;mb_uri, "Name-URI: ");
 
 
   /* Want a self-signed certificate?  */
&lt;/pre&gt;</description>
    <dc:creator>NIIBE Yutaka</dc:creator>
    <dc:date>2012-04-26T00:55:48</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16893">
    <title>[PATCH] simplify ldap URL construction</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16893</link>
    <description>&lt;pre&gt;
* dirmngr/ldap-url.c (ldap_charray2str): Remove unwarranted uses of
strncpy, and simplify.
---
Looking at the other strncpy uses, I found these two and saw that they
are unnecessary, since we know in each case that the specified length
is also the length of the source string.  Using stpcpy makes it
simpler/clearer.

 dirmngr/ldap-url.c |    9 ++-------
 1 file changed, 2 insertions(+), 7 deletions(-)

diff --git a/dirmngr/ldap-url.c b/dirmngr/ldap-url.c
index 7b27a30..47441b1 100644
--- a/dirmngr/ldap-url.c
+++ b/dirmngr/ldap-url.c
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -342,16 +342,11 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; char * ldap_charray2str( char **a, const char *sep )
 p = s;
 for ( v = a; *v != NULL; v++ ) {
 if ( v != a ) {
-strncpy( p, sep, slen );
-p += slen;
+p = stpncpy( p, sep, slen );
 }
-
-len = strlen( *v );
-strncpy( p, *v, len );
-p += len;
+p = stpcpy( p, *v );
 }

-*p = '\0';
 return s;
 }

--
1.7.10.335.g879d8
&lt;/pre&gt;</description>
    <dc:creator>Jim Meyering</dc:creator>
    <dc:date>2012-04-25T15:44:46</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16892">
    <title>[PATCH 1] remove doubled words in a comment</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16892</link>
    <description>&lt;pre&gt;
---
 common/gettime.h |    6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/common/gettime.h b/common/gettime.h
index 4199369..bc914ad 100644
--- a/common/gettime.h
+++ b/common/gettime.h
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -1,5 +1,5 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
 /* gettime.h - Wrapper for time functions
- * Copyright (C) 2010 Free Software Foundation, Inc.
+ * Copyright (C) 2010, 2012 Free Software Foundation, Inc.
  *
  * This file is part of GnuPG.
  *
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -24,8 +24,8 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
 #include &amp;lt;gpg-error.h&amp;gt; /* We need gpg_error_t. */


-/* A type to hold the ISO time.  Note that this this is the same as
-   the the KSBA type ksba_isotime_t. */
+/* A type to hold the ISO time.  Note that this is the same as
+   the KSBA type ksba_isotime_t. */
 typedef char gnupg_isotime_t[16];

 time_t gnupg_get_time (void);
--
1.7.10.335.g879d8
&lt;/pre&gt;</description>
    <dc:creator>Jim Meyering</dc:creator>
    <dc:date>2012-04-25T15:40:48</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16891">
    <title>[PATCH] avoid buffer strncpy-induced buffer overrun</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16891</link>
    <description>&lt;pre&gt;
* dirmngr/crlcache.c (open_dir): Ensure that both this_update
and next_update member strings are NUL-terminated.
---
this_update and next_update are sometimes expected to
be NUL-terminated strings, we must ensure it here.
Otherwise, the readers may access beyond the end of those buffers.

 dirmngr/crlcache.c |   10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/dirmngr/crlcache.c b/dirmngr/crlcache.c
index edf3837..768d446 100644
--- a/dirmngr/crlcache.c
+++ b/dirmngr/crlcache.c
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -587,8 +587,14 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; open_dir (crl_cache_t *r_cache)
                 case 2: entry-&amp;gt;issuer_hash = p; break;
                 case 3: entry-&amp;gt;issuer = unpercent_string (p); break;
                 case 4: entry-&amp;gt;url = unpercent_string (p); break;
-                case 5: strncpy (entry-&amp;gt;this_update, p, 15); break;
-                case 6: strncpy (entry-&amp;gt;next_update, p, 15); break;
+                case 5:
+  strncpy (entry-&amp;gt;this_update, p, 15);
+  entry-&amp;gt;this_update[15] = 0;
+  break;
+              &lt;/pre&gt;</description>
    <dc:creator>Jim Meyering</dc:creator>
    <dc:date>2012-04-25T15:42:53</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16888">
    <title>[PATCH] tools/gpgsm-gencert.sh</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16888</link>
    <description>&lt;pre&gt;Hello,

gpgsm-gencert.sh doesn't work well with dash (version 0.5.7).

When URI_ADDRESSES is null, it exits without emitting
CSR.  It exits after the line:

[ -n "$URI_ADDRESSES" ] &amp;amp;&amp;amp; echo "$URI_ADDRESSES"

When I change it to:

[ -n "$URI_ADDRESSES" ] &amp;amp;&amp;amp; echo "$URI_ADDRESSES" || exit 0

it works.

It seems that dash's subshell with -e behavior is different.

Following is a patch to fix this problem, by not using subshell.

This works with both of dash and bash.

----------------------
diff --git a/tools/gpgsm-gencert.sh b/tools/gpgsm-gencert.sh
index b209c8e..28c3792 100755
--- a/tools/gpgsm-gencert.sh
+++ b/tools/gpgsm-gencert.sh
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -171,7 +171,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; file_parameter=$(mktemp "/tmp/gpgsm.XXXXXX")
 outfile=$(mktemp "/tmp/gpgsm.XXXXXX")
 

-(
+{
 cat &amp;lt;&amp;lt;EOF
 Key-Type: $KEY_TYPE
 Key-Length: $KEY_LENGTH
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -182,7 +182,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; EOF
 [ -n "$EMAIL_ADDRESSES" ] &amp;amp;&amp;amp; echo "$EMAIL_ADDRESSES"
 [ -n "$DNS_ADDRESSES" ] &amp;amp;&amp;amp; echo "$DNS_ADDRESSES"
 [ -n "$URI_ADDRESSES" ] &amp;amp;&amp;amp; echo "$URI_ADDRESSES"
-) &amp;gt; "$file_parameter"
+} &amp;gt; "$fil&lt;/pre&gt;</description>
    <dc:creator>NIIBE Yutaka</dc:creator>
    <dc:date>2012-04-25T02:33:03</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16887">
    <title>GnuPG 2.0 decryption of two PGP Message blocks in one Message</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16887</link>
    <description>&lt;pre&gt;Dear Developer,

Here's a peculiar scenario, I have a file which has 2 pgp messages or
blocks embedded in a single file one below the other.

Can GPG 2.0 be able to decrypt both the blocks and concatenate the messages
inside same single file?

I have attached the sample PGP file for reference and more clear picture of
the scenario.

Any help is greatly appreciated.

Thanks.
&lt;/pre&gt;</description>
    <dc:creator>Ajay Kallur</dc:creator>
    <dc:date>2012-04-24T16:13:48</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16880">
    <title>[PATCH 0/2] gitignore and string.h updates for GPGME</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16880</link>
    <description>&lt;pre&gt;While I'm waiting for the go-ahead for more major socket changes to
GPGME, here are a few more minor cleanups.  I think I got the ChangeLog
commit message format right this time ;).


W. Trevor King (2):
  .gitignore: flesh out rules and add subdirectory-.gitignores.
  status-table.c: include string.h for strcmp.

 .gitignore                |   13 ++++++++-----
 doc/.gitignore            |    5 +++++
 lang/cl/.gitignore        |    1 +
 src/.gitignore            |    7 +++++++
 src/status-table.c        |    1 +
 tests/.gitignore          |   10 ++++++++++
 tests/gpg/.gitignore      |   30 ++++++++++++++++++++++++++++++
 tests/gpgsm/.gitignore    |   17 +++++++++++++++++
 tests/opassuan/.gitignore |    3 +++
 9 files changed, 82 insertions(+), 5 deletions(-)
 create mode 100644 doc/.gitignore
 create mode 100644 lang/cl/.gitignore
 create mode 100644 src/.gitignore
 create mode 100644 tests/.gitignore
 create mode 100644 tests/gpg/.gitignore
 create mode 100644 tests/gpgsm/.gitignore
 create mode 100644 test&lt;/pre&gt;</description>
    <dc:creator>W. Trevor King</dc:creator>
    <dc:date>2012-04-12T17:51:47</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16873">
    <title>Unable to compile libassuan-git</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16873</link>
    <description>&lt;pre&gt;Hello,

I'm trying to maintain as much as I can the ArchLinux AUR package for
GnuPG2-git. To build the latest version libassuan&amp;gt;2.1 and ntph are
mandatory. Building ntph was an easy one but I'm getting an error with
libassuan-git. Can someone give me a hint?

Thanks
alphazo

.....
mv -f .deps/funopen.Tpo .deps/funopen.Plo
/bin/sh ../libtool --tag=CC   --mode=link gcc  -march=x86-64
-mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4
-D_FORTIFY_SOURCE=2 -Wall -Wcast-align -Wshadow -Wstrict-prototypes
-Wpointer-arith -fPIC -DPIC    -Wl,--version-script=./libassuan.vers
-version-info 3:0:3
-Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu -o
libassuan.la -rpath /usr/lib  libassuan_la-assuan.lo
libassuan_la-context.lo libassuan_la-system.lo libassuan_la-debug.lo
libassuan_la-conversion.lo libassuan_la-sysutils.lo
libassuan_la-client.lo libassuan_la-server.lo
libassuan_la-assuan-error.lo libassuan_la-assuan-buffer.lo
libassuan_la-assuan-handler.lo libassuan_la-assuan-inquire.lo
libassua&lt;/pre&gt;</description>
    <dc:creator>Alphazo</dc:creator>
    <dc:date>2012-04-11T21:50:48</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16861">
    <title>gnupg-2.0.19 test failures on GNU/Linux Red Hat 5.8 IA-64 (Itanium)</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16861</link>
    <description>&lt;pre&gt;I've just made a series of experiments with builds of gnupg-2.0.19 on
Red Hat 5.8 IA-64 (Itanium) with multiple compilers:

cc  (GCC) 4.1.2 20080704 (Red Hat 4.1.2-52)

gcc (GCC) 4.1.3 20080630 (prerelease)
gcc (GCC) 4.2.5 20090325 (prerelease)
gcc (GCC) 4.3.0 20071123 (experimental)
gcc (GCC) 4.4.6 20110301 (prerelease)
gcc (GCC) 4.5.3 20110303 (prerelease)
gcc (GCC) 4.6.1 20110429 (prerelease)
gcc (GCC) 4.7.0 20110430 (experimental)

icc (ICC) 9.1 20080314

Only the build with icc passed all of the tests, so I have
installed that one.

Builds typically look like this:

env CC=gcc-4.7 CFLAGS=-I/usr/local/include ./configure --libdir=/usr/local/lib &amp;amp;&amp;amp; make all check

With the 8 different gcc versions, I get one or two test failures:

cc
3DES FAIL: conventional-mdc.test

gcc-4.1
FAIL: genkey1024.test
3DES FAIL: conventional-mdc.test

gcc-4.2
FAIL: genkey1024.test
FAIL: conventional.test

gcc-4.3
FAIL: conventional.test

gcc-4.4
FAIL: genkey1024.test

gcc-4.5
FAIL: genkey1024.te&lt;/pre&gt;</description>
    <dc:creator>Nelson H. F. Beebe</dc:creator>
    <dc:date>2012-04-05T15:46:39</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16860">
    <title>gnupg-2.0.19: make distclean removes critical file</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16860</link>
    <description>&lt;pre&gt;A "make distclean" operation in gnupg-2.0.19 removes a
critical file: 

make[1]: Entering directory `/export/home/build/bare/gnupg-2.0.19/common'
test -z "audit-events.h status-codes.h" || rm -f audit-events.h status-codes.h

common/audit-events.h is part of the original distribution,
and gnupg-2.0.19 cannot be rebuilt without it.

-------------------------------------------------------------------------------
- Nelson H. F. Beebe                    Tel: +1 801 581 5254                  -
- University of Utah                    FAX: +1 801 581 4148                  -
- Department of Mathematics, 110 LCB    Internet e-mail: beebe&amp;lt; at &amp;gt;math.utah.edu  -
- 155 S 1400 E RM 233                       beebe&amp;lt; at &amp;gt;acm.org  beebe&amp;lt; at &amp;gt;computer.org -
- Salt Lake City, UT 84112-0090, USA    URL: http://www.math.utah.edu/~beebe/ -
-------------------------------------------------------------------------------
&lt;/pre&gt;</description>
    <dc:creator>Nelson H. F. Beebe</dc:creator>
    <dc:date>2012-04-05T12:54:20</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16857">
    <title>scd: a race condition between scd_command_handler and handle_tick</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16857</link>
    <description>&lt;pre&gt;This is a bug report for GnuPG 2.0.19 (or 2.0.18).  I have not yet
checked if there is this bug in the development version or not.

This bug was found at "make check" of building scute 1.4.0 for Debian.
I think that it is a bug of a race condition.

Here are failure logs:

https://buildd.debian.org/status/fetch.php?pkg=scute&amp;amp;arch=armel&amp;amp;ver=1.4.0-2&amp;amp;stamp=1333006067
https://buildd.debian.org/status/fetch.php?pkg=scute&amp;amp;arch=ia64&amp;amp;ver=1.4.0-3&amp;amp;stamp=1333361223

It surely occured on other non-exotic architectures.  In fact, I
encountered on my amd64 box too (sorry, I lost the log).


NORMAL CASE:
Since the build environment doesn't have libpcsclite.so.1, pcsc daemon
wrappers fails at start up, and it results "Card error".

In the log, it's like:
-----------------------
gpg-agent[27706]: can't create directory `/home/buildd/.gnupg': No such file or directory
scdaemon[27707]: error sending PC/SC OPEN request: Broken pipe
gpg-agent[27706]: command learn failed: Card error
Skipping test because no token is present.
PAS&lt;/pre&gt;</description>
    <dc:creator>Niibe Yutaka</dc:creator>
    <dc:date>2012-04-04T01:43:55</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16854">
    <title>gnupg-2.0.19: common/estream.c mixes void and int</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16854</link>
    <description>&lt;pre&gt;While builds of gnupg-2.0.19 were successful on most of my roughly
25 flavors of Unix, compilations fail on two Solaris Intel systems.
The cause appears to be mixing of void and int in the file
common/estream.c in the definitions of the macros
ESTREAM_MUTEX_LOCK() .. ESTREAM_MUTEX_INITIALIZE() in
lines 177--188.

In function es_ftrylockfile() at line 2619, the value of
ESTREAM_TRYLOCK() is returned as an int, but a void cannot
be cast to an int.

Another minor problem is that configure.ac at line 1473 says

*** It is now required to build with support for the
*** GNU Portable Threads Library (Pth).

However, running 

% ./configure --help | grep pth
  --with-pth-prefix=PFX   prefix where GNU Pth is installed (optional)

says that Pth is optional.  Either it is optional, or it is
required, but only one can be true.

-------------------------------------------------------------------------------
- Nelson H. F. Beebe                    Tel: +1 801 581 5254                  -
- University of Utah                &lt;/pre&gt;</description>
    <dc:creator>Nelson H. F. Beebe</dc:creator>
    <dc:date>2012-03-28T16:06:23</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16847">
    <title>[Announce] GnuPG 2.0.19 released</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16847</link>
    <description>&lt;pre&gt;Hello!

We are pleased to announce the availability of a new stable GnuPG-2
release:  Version 2.0.19.

The GNU Privacy Guard (GnuPG) is GNU's tool for secure communication
and data storage.  It can be used to encrypt data, create digital
signatures, help authenticating using Secure Shell and to provide a
framework for public key cryptography.  It includes an advanced key
management facility and is compliant with the OpenPGP and S/MIME
standards.

GnuPG-2 has a different architecture than GnuPG-1 (e.g. 1.4.12) in
that it splits up functionality into several modules.  However, both
versions may be installed alongside without any conflict.  In fact,
the gpg version from GnuPG-1 is able to make use of the gpg-agent as
included in GnuPG-2 and allows for seamless passphrase caching.  The
advantage of GnuPG-1 is its smaller size and the lack of dependency on
other modules at run and build time.  We will keep maintaining GnuPG-1
versions because they are very useful for small systems and for server
based application&lt;/pre&gt;</description>
    <dc:creator>Werner Koch</dc:creator>
    <dc:date>2012-03-27T09:20:14</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16841">
    <title>bug tracker is down</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16841</link>
    <description>&lt;pre&gt;Hi!

Our bug tracker is currently down.  I'll fix it tomorrow.


Salam-Shalom,

   Werner

&lt;/pre&gt;</description>
    <dc:creator>Werner Koch</dc:creator>
    <dc:date>2012-03-20T21:06:06</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16836">
    <title>Stable GnuPG: 1.4.12 vs 2.0.18</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16836</link>
    <description>&lt;pre&gt;Dear GnuPG developers,

Over at Arch Linux (see [1] and surrounding messages) we are slightly
confused by the statuses of GnuPG-1 and GnuPG-2, and more specifically
the following sentences:

"1.4.12 is the stable version of GnuPG. (2.0.18 is the unstable
development version)." [2]

"We are pleased to announce the availability of a new stable
GnuPG-2 release:  Version 2.0.18." [3]

We understand the GnuPG-2 branch is very different to GnuPG-1. Hence our
question: will you consider the GnuPG-2 branch as stable as GnuPG-1 some
day in the future, or is this already the case?

Cheers.

[1] http://mailman.archlinux.org/pipermail/arch-dev-public/2012-March/022704.html
[2] http://www.gnupg.org/download/release_notes.en.html
[3] http://lists.gnupg.org/pipermail/gnupg-announce/2011q3/000312.html

&lt;/pre&gt;</description>
    <dc:creator>Gaetan Bisson</dc:creator>
    <dc:date>2012-03-19T06:20:14</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16828">
    <title>secure memory for decryption buffer</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16828</link>
    <description>&lt;pre&gt;Hello,

I sent a previous message (subject: gpgme not using secure memory?) to
the list but I assume it got lost in moderation (was not subscribed).

I'm writing a password manager and want it to use a gpg-encrypted file
for storing passwords. I figured that gpgme would be the right tool to
use to integrate gpg encryption/decryption in my application. However,
I'm unsure if gpgme stores decrypted data in secure memory. I don't want
passwords to be swapped to disk.

As far as I can tell from peeking at the gpgme source code, it reads
decrypted data using assuan_read_line, and I cannot find any mlock's
either in libassuan nor in gpgme.

I'm new to the gpg-related libraries so I might very well have missed
something, could someone please confirm if decrypted data can indeed be
swapped when using gpgme?

Thanks in advance!

/Martin
_______________________________________________
Gnupg-devel mailing list
Gnupg-devel&amp;lt; at &amp;gt;gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-devel
&lt;/pre&gt;</description>
    <dc:creator>Martin Stenberg</dc:creator>
    <dc:date>2012-03-16T16:31:26</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16826">
    <title>gpg-agent and AIX</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16826</link>
    <description>&lt;pre&gt;We have GnuPG 2.0.18 built on AIX. gpg-agent --help takes forever to
start. The reason is because get_max_fds() in common/exechelp.c
returns 2147483647 for max_fds. This is regardless of the limit placed
on file descriptors:
  $ limit
  cputime         unlimited
  filesize        unlimited
  datasize        unlimited
  stacksize       128MB
  coredumpsize    unlimited
  resident        unlimited
  addressspace    unlimited
  descriptors     2048

So I guess we have to come up with an alternate way to get the max_fds
on this platform?

&lt;/pre&gt;</description>
    <dc:creator>Albert Chin</dc:creator>
    <dc:date>2012-03-15T17:41:57</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16814">
    <title>2.1.0beta3 missing man pages?</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.devel/16814</link>
    <description>&lt;pre&gt;it looks to me like the following binaries in 2.1.0beta3 don't yet have 
a manual page:

  gpg-check-pattern
  kbxutil
  g13
  gpgkey2ssh

Are there plans to document them with manual pages?

There is also a manpage for gpg-zip.1, but the tool appears to be named 
gpgtar.

Thanks (and apologies for the minor flood here, i'm trying to document 
the issues as i see them)

--dkg
&lt;/pre&gt;</description>
    <dc:creator>Daniel Kahn Gillmor</dc:creator>
    <dc:date>2012-03-14T06:55:09</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.encryption.gpg.devel">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.encryption.gpg.devel</link>
  </textinput>
</rdf:RDF>

