Debian Bug report logs - #499569
gnupg-agent: modifies SigBlk mask of all processes spawned in the X session breaking unrelated software [i386 only?]

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Mirco Bauer <meebey@debian.org>

To: submit@bugs.debian.org

Subject: gnupg-agent: modifies SigBlk mask of all processes spawned in the X session breaking unrelated software

Date: Fri, 19 Sep 2008 23:26:23 +0200

[Message part 1 (text/plain, inline)]

Package: gnupg-agent
Version: 2.0.9-3
Severity: critical

gnupg-agent somehow manages to change the SigBlk mask causing all child
processes that are spawned part of the X session to have the SigBlk
mask set causing real-time signals to be blocked. This breaks all
applications spawned in that X session that rely on
real-time signals.

As this breaks unrelated software I set the severity to critical.

Here the summary of my full investigation:
About 2 months ago I started to suffer from an issue that first looked
like a bug in Mono's threading implementation. The test-case to
reproduce it looks like this:

Attachment:
test-thread-abort.cs

Compile:
mcs test-thread-abort.cs

Run:
mono test-thread-abort.exe

My output:
thread.Start()
Worker(): thread started
Worker(): working... 0
Worker(): working... 1
Worker(): working... 2
Worker(): working... 3
Worker(): working... 4
thread.Abort()
press enter to quit!
Worker(): working... 5
Worker(): working... 6
Worker(): working... 7
Worker(): working... 8
Worker(): working... 9
Worker(): working... 10
Worker(): working... 11
Worker(): working... 12
(continuing forever -> killed using ^C)

The expected output:
thread.Start()
Worker(): thread started
Worker(): working... 0
Worker(): working... 1
Worker(): working... 2
Worker(): working... 3
Worker(): working... 4
thread.Abort()
press enter to quit!
Worker(): thread aborted!
Worker(): thread ended

The thread was never aborted and thus forever continued on my system.
After more investigation in Mono's threading implementation I found
that it uses real-time signals to control the threads. A strace then
showed that the signal (SIGRT1) was send but never received.... This
made me really curious.

So I wrote a C test-case for this issue, which looks like this:

Attachment:
test-signal.c

Compile:
gcc test-signal.c -o test-signal

Run:
./test-signal

My Output:
SIGRTMIN: 34
sigismember(): 1
SIGRTMIN is blocked, trying to unblock...done.
sigismember(): 0
SIGRT_1 received
SIGRT_2 received
SIGQUIT received

The expected output:
SIGRTMIN: 34
sigismember(): 0
SIGRT_1 received
SIGRT_2 received
SIGQUIT received

And that proved the signal (SIGRT) is indeed already blocked when the
application is started.

Then I found out / learned that blocking signals is a feature and the
SigBlk mask is inherited to child processes. So something was setting
this mask, and I could not find out what it was till today.

I reinstalled my system (1 week ago) after I could not find the exact
cause of this issue (after 3 continuous days of investigation)
and today it started to happen again, after I was sponsoring a package
upload, for which I had to install pscd and gnupg-agent to get my
crypto card working again (after the reinstall).

Then I disabled the gpg-agent in my ~/.gnupg/gpg.conf, restarted my X
session and viola SigBlk mask is back to normal and all my lovely
applications work again like they should.

Enabling the gpg-agent in ~/.gnupg/gpg.conf again brings the issue back.

I noticed the gpg-agent is started in /etc/X11/Xsession.d/90gpg-agent,
but I no have no idea how it manages to change (or rather inherits) the
SigBlk mask of other processes spawned in the X session....

Here also a little detection script I wrote to identify processes with
that set SigBlk mask (it also finds some "false-positives" as some apps
really need that mask, but not _all_ processes launched under the X
session!)

Attachment:
proc-sigblk.sh:

My output:
Name:	x-session-manag
Pid:	21699
Uid:	1000	1000	1000	1000
Gid:	1000	1000	1000	1000
Name:	dbus-launch
Pid:	21757
Uid:	1000	1000	1000	1000
Gid:	1000	1000	1000	1000
Name:	dbus-daemon
Pid:	21758
Uid:	1000	1000	1000	1000
Gid:	1000	1000	1000	1000
Name:	seahorse-agent
Pid:	21764
Uid:	1000	1000	1000	1000
Gid:	1000	1000	1000	1000
Name:	gnome-settings-
Pid:	21769
Uid:	1000	1000	1000	1000
Gid:	1000	1000	1000	1000
Name:	metacity
Pid:	21781
Uid:	1000	1000	1000	1000
Gid:	1000	1000	1000	1000
Name:	gnome-panel
Pid:	21782
Uid:	1000	1000	1000	1000
Gid:	1000	1000	1000	1000
Name:	nautilus
Pid:	21783
Uid:	1000	1000	1000	1000
Gid:	1000	1000	1000	1000
Name:	gnome-screensav
Pid:	21786
Uid:	1000	1000	1000	1000
Gid:	1000	1000	1000	1000
Name:	gnome-vfs-daemo
Pid:	21795
Uid:	1000	1000	1000	1000
Gid:	1000	1000	1000	1000
Name:	bluetooth-apple
Pid:	21798
Uid:	1000	1000	1000	1000
Gid:	1000	1000	1000	1000
Name:	gnome-do
Pid:	21799
Uid:	1000	1000	1000	1000
Gid:	1000	1000	1000	1000
Name:	update-notifier
Pid:	21803
Uid:	1000	1000	1000	1000
Gid:	1000	1000	1000	1000
Name:	gnome-do
Pid:	21804
Uid:	1000	1000	1000	1000
Gid:	1000	1000	1000	1000
Name:	system-config-p
Pid:	21811
Uid:	1000	1000	1000	1000
Gid:	1000	1000	1000	1000
Name:	kerneloops-appl
Pid:	21815
Uid:	1000	1000	1000	1000
Gid:	1000	1000	1000	1000
Name:	gnome-volume-ma
Pid:	21817
Uid:	1000	1000	1000	1000
Gid:	1000	1000	1000	1000
Name:	nm-applet
Pid:	21819
Uid:	1000	1000	1000	1000
Gid:	1000	1000	1000	1000
Name:	gnome-power-man
Pid:	21827
Uid:	1000	1000	1000	1000
Gid:	1000	1000	1000	1000
Name:	multiload-apple
Pid:	21849
Uid:	1000	1000	1000	1000
Gid:	1000	1000	1000	1000
Name:	mixer_applet2
Pid:	21852
Uid:	1000	1000	1000	1000
Gid:	1000	1000	1000	1000
Name:	gweather-applet
Pid:	21855
Uid:	1000	1000	1000	1000
Gid:	1000	1000	1000	1000
Name:	locate
Pid:	21862
Uid:	1000	1000	1000	1000
Gid:	1000	105	105	105
Name:	locate
Pid:	21863
Uid:	1000	1000	1000	1000
Gid:	1000	105	105	105
Name:	mapping-daemon
Pid:	21866
Uid:	1000	1000	1000	1000
Gid:	1000	1000	1000	1000
Name:	gnome-terminal
Pid:	21868
Uid:	1000	1000	1000	1000
Gid:	1000	1000	1000	1000
Name:	gnome-pty-helpe
Pid:	21871
Uid:	1000	1000	1000	1000
Gid:	1000	43	43	43
Name:	bonobo-activati
Pid:	3878
Uid:	1000	1000	1000	1000
Gid:	1000	1000	1000	1000
Name:	egrep
Pid:	22046
Uid:	1000	1000	1000	1000
Gid:	1000	1000	1000	1000

The expected output:
(none or a very small set of applications like gconfd-2 or some
gnome applets)

-- 
Regards,

Mirco 'meebey' Bauer

PGP-Key ID: 0xEEF946C8

FOSS Developer    meebey@meebey.net  http://www.meebey.net/
PEAR Developer    meebey@php.net     http://pear.php.net/
Debian Developer  meebey@debian.org  http://www.debian.org/

[test-signal.c (text/x-csrc, attachment)]

[test-thread-abort.cs (text/x-csharp, attachment)]

[proc-sigblk.sh (application/x-shellscript, attachment)]

Message #10 received at 499569@bugs.debian.org (full text, mbox, reply):

From: Mirco Bauer <meebey@debian.org>

To: 499569@bugs.debian.org

Subject: more details about the sigblk issue

Date: Fri, 3 Oct 2008 23:33:39 +0200

retitle 499569 gnupg-agent: modifies SigBlk mask of all processes spawned in the X session breaking unrelated software [i386 only?]

Hi again,

Thomas Viehmann was so nice and contacted me about this issue on IRC.
He could _not_ reproduce the issue on his amd64 system.

Someone else (Ingo) could reproduce this issue on his i386 (dual-core) system but
not on his amd64 system.

Someone else (Rene) could _not_ reproduce this issue on his ppc system.

Someone else (jonnylamb) could _not_ reproduce this issue on his sparc system.
He could reproduce this issue on his i386 (single-core) system.

I use i386 (quad-core) too. So we can assume this issue might be i386 specific!

We have now a one-liner to reproduce this bug:
gpg-agent --daemon grep SigBlk /proc/self/status

That should output:
SigBlk:	0000000000000000

But on the said i386 systems it outputs:
SigBlk:	fffffffe00000000

For a while we thought this issue is maybe related to my specific
use-case, that is using the PC/SC / CCID / SSH support. But this
doesn't seem to be related as tests with a clean user (empty $HOME)
shows the same result.

-- 
Regards,

Mirco 'meebey' Bauer

PGP-Key ID: 0xEEF946C8

FOSS Developer    meebey@meebey.net  http://www.meebey.net/
PEAR Developer    meebey@php.net     http://pear.php.net/
Debian Developer  meebey@debian.org  http://www.debian.org/

Message #17 received at 499569@bugs.debian.org (full text, mbox, reply):

From: Thomas Viehmann <tv@beamnet.de>

To: 499569@bugs.debian.org

Subject: gnupg2: diff for NMU version 2.0.9-3.1

Date: Sat, 04 Oct 2008 12:12:55 +0200

tags 499569 + patch pending
thanks

Hi gnupg2-maintainers,

Here is the NMU for gnupg2 (versioned as 2.0.9-3.1).
pth seems to mess with the sigprocmask on i386 at least. As such
deinitializing pth (with pth_kill) before execv seems like a good idea.
Because that does not quite do the trick, I also "manually" save
and restore the sigprogmask.
Regarding the problem of reproducing, I should add to Mirco's comments
that it apparently only occurs when running in a i386 kernel, not in an
i386 chroot on and amd64 system.
After some more testing, I will upload the NMU.

Kind regards

T.

diff -u gnupg2-2.0.9/debian/changelog gnupg2-2.0.9/debian/changelog
--- gnupg2-2.0.9/debian/changelog
+++ gnupg2-2.0.9/debian/changelog
@@ -1,3 +1,12 @@
+gnupg2 (2.0.9-3.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * agent/gpg-agent.c: Deinit the threading library before exec'ing
+    the command to run in --daemon mode. And because that still doesn't
+    restore the sigprocmask, do that manually. Closes: #499569
+
+ -- Thomas Viehmann <tv@beamnet.de>  Sat, 04 Oct 2008 10:25:53 +0200
+
 gnupg2 (2.0.9-3) unstable; urgency=medium
 
   * Urgency medium to try to beat the release.
only in patch2:
unchanged:
--- gnupg2-2.0.9.orig/agent/gpg-agent.c
+++ gnupg2-2.0.9/agent/gpg-agent.c
@@ -490,6 +490,8 @@
   int use_standard_socket = 0;
   gpg_error_t err;
   const char *env_file_name = NULL;
+  sigset_t initial_sigs;
+  
 
 
   set_strusage (my_strusage);
@@ -499,6 +501,8 @@
      somewhere after the option parsing */
   log_set_prefix ("gpg-agent", JNLIB_LOG_WITH_PREFIX|JNLIB_LOG_WITH_PID); 
 
+  sigprocmask(SIG_SETMASK, NULL, &initial_sigs);
+   
   /* Make sure that our subsystems are ready.  */
   init_common_subsystems ();
 
@@ -1004,6 +1008,14 @@
                   kill (pid, SIGTERM );
                   exit (1);
                 }
+              if (! pth_kill()) 
+		{
+                  log_error ("failed to clean up threading");
+                  kill (pid, SIGTERM );
+                  exit (1);
+		}
+	      sigprocmask(SIG_SETMASK, &initial_sigs, NULL);
+
               execvp (argv[0], argv);
               log_error ("failed to run the command: %s\n", strerror (errno));
               kill (pid, SIGTERM);

Message #24 received at 499569-close@bugs.debian.org (full text, mbox, reply):

From: Thomas Viehmann <tv@beamnet.de>

To: 499569-close@bugs.debian.org

Subject: Bug#499569: fixed in gnupg2 2.0.9-3.1

Date: Sat, 04 Oct 2008 21:02:10 +0000

Source: gnupg2
Source-Version: 2.0.9-3.1

We believe that the bug you reported is fixed in the latest version of
gnupg2, which is due to be installed in the Debian FTP archive:

gnupg-agent_2.0.9-3.1_amd64.deb
  to pool/main/g/gnupg2/gnupg-agent_2.0.9-3.1_amd64.deb
gnupg2_2.0.9-3.1.diff.gz
  to pool/main/g/gnupg2/gnupg2_2.0.9-3.1.diff.gz
gnupg2_2.0.9-3.1.dsc
  to pool/main/g/gnupg2/gnupg2_2.0.9-3.1.dsc
gnupg2_2.0.9-3.1_amd64.deb
  to pool/main/g/gnupg2/gnupg2_2.0.9-3.1_amd64.deb
gpgsm_2.0.9-3.1_amd64.deb
  to pool/main/g/gnupg2/gpgsm_2.0.9-3.1_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 499569@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Viehmann <tv@beamnet.de> (supplier of updated gnupg2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Sat, 04 Oct 2008 10:25:53 +0200
Source: gnupg2
Binary: gnupg-agent gpgsm gnupg2
Architecture: source amd64
Version: 2.0.9-3.1
Distribution: unstable
Urgency: low
Maintainer: Eric Dorland <eric@debian.org>
Changed-By: Thomas Viehmann <tv@beamnet.de>
Description: 
 gnupg-agent - GNU privacy guard - password agent
 gnupg2     - GNU privacy guard - a free PGP replacement
 gpgsm      - GNU privacy guard - S/MIME version
Closes: 499569
Changes: 
 gnupg2 (2.0.9-3.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * agent/gpg-agent.c: Deinit the threading library before exec'ing
     the command to run in --daemon mode. And because that still doesn't
     restore the sigprocmask, do that manually. Closes: #499569
Checksums-Sha1: 
 7ea431c20af542c390549d3c47ca167d9a25a6ec 1362 gnupg2_2.0.9-3.1.dsc
 76449de5f5a4b57bb3e3207cfd9fe26926041295 40261 gnupg2_2.0.9-3.1.diff.gz
 57560a2160cd63949467c4ef143f5303bd7312ff 316324 gnupg-agent_2.0.9-3.1_amd64.deb
 a67be8bc8a5e6b7fc36416499427c7c53514a620 463176 gpgsm_2.0.9-3.1_amd64.deb
 3094faebcc1ff5bc3e0a95df24e1c218e196a4d5 2183752 gnupg2_2.0.9-3.1_amd64.deb
Checksums-Sha256: 
 531ea81e97b88f275880a08075360bf6ec3343544958696eddf8138dcfb25cfa 1362 gnupg2_2.0.9-3.1.dsc
 82aa02d999376c2c19695e408a4ed68f707c2246d8207c576edfa3e06a261272 40261 gnupg2_2.0.9-3.1.diff.gz
 9e5ba276ddfcff41810f92df2adc4f8b6376762a132e458c1c7fbc28bfbbda48 316324 gnupg-agent_2.0.9-3.1_amd64.deb
 f8771d612bd630c36b243a0a4be8886c7c382bac146c865e5be4ea58d84c89e6 463176 gpgsm_2.0.9-3.1_amd64.deb
 046287105a95b3ab02156da035f12b8c1f2b56f2a754c5667c6be388fc9d28b2 2183752 gnupg2_2.0.9-3.1_amd64.deb
Files: 
 f7a7fa98ed5409bc91f740df4d8e3c55 1362 utils optional gnupg2_2.0.9-3.1.dsc
 32bcaadb77e5755d335076dcd6ee49eb 40261 utils optional gnupg2_2.0.9-3.1.diff.gz
 978cad7ec48e0188e11e548251a99707 316324 utils optional gnupg-agent_2.0.9-3.1_amd64.deb
 c97f44db2d3084c78391759bc16ecdd0 463176 utils optional gpgsm_2.0.9-3.1_amd64.deb
 0897f52a39b25347be1a92d40d77ca4e 2183752 utils optional gnupg2_2.0.9-3.1_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkjnvmwACgkQriZpaaIa1PlsFgCgwLMSQp3EKsdhqy3kII4fEOyV
uWwAn2MrMEzNOtAnoi5tUBWlaTSvFXZ3
=T+U2
-----END PGP SIGNATURE-----

Message #37 received at 499569@bugs.debian.org (full text, mbox, reply):

From: Mirco Bauer <meebey@debian.org>

To: 499569@bugs.debian.org

Subject: regression in gnupg-agent 2.0.11-1

Date: Thu, 21 May 2009 22:09:23 +0200

unarchive 499569
reopen 499569
found 499569 2.0.11-1
thanks

gnupg-agent 2.0.11-1 has a regression, see:

meebey@redbull:~$ gpg-agent --daemon grep SigBlk /proc/self/status
SigBlk:	fffffffe00000000
meebey@redbull:~$ 

Looking at the gnupg2 PTS page it seems like the 2.0.9-3.1 NMU done by
Thomas Viehmann was not incorporated into the package.

-- 
Regards,

Mirco 'meebey' Bauer

PGP-Key ID: 0xEEF946C8

FOSS Developer    meebey@meebey.net  http://www.meebey.net/
PEAR Developer    meebey@php.net     http://pear.php.net/
Debian Developer  meebey@debian.org  http://www.debian.org/

Message #46 received at 499569@bugs.debian.org (full text, mbox, reply):

From: "Daniel Leidert" <daniel.leidert@wgdd.de>

To: 499569@bugs.debian.org

Cc: 499569-submitter@bugs.debian.org, "Mirco Bauer" <meebey@debian.org>

Subject: Bug#499569: regression in gnupg-agent 2.0.11-1

Date: Tue, 2 Jun 2009 18:03:04 +0200 (CEST)

Should be fixed upstream:

http://lists.gnupg.org/pipermail/gnupg-commits/2009-June/008271.html
https://bugs.g10code.com/gnupg/issue1066

Regards, Daniel

Message #56 received at 499569-close@bugs.debian.org (full text, mbox, reply):

From: Eric Dorland <eric@debian.org>

To: 499569-close@bugs.debian.org

Subject: Bug#499569: fixed in gnupg2 2.0.12-1

Date: Mon, 24 Aug 2009 01:17:11 +0000

Source: gnupg2
Source-Version: 2.0.12-1

We believe that the bug you reported is fixed in the latest version of
gnupg2, which is due to be installed in the Debian FTP archive:

gnupg-agent_2.0.12-1_amd64.deb
  to pool/main/g/gnupg2/gnupg-agent_2.0.12-1_amd64.deb
gnupg2_2.0.12-1.diff.gz
  to pool/main/g/gnupg2/gnupg2_2.0.12-1.diff.gz
gnupg2_2.0.12-1.dsc
  to pool/main/g/gnupg2/gnupg2_2.0.12-1.dsc
gnupg2_2.0.12-1_amd64.deb
  to pool/main/g/gnupg2/gnupg2_2.0.12-1_amd64.deb
gnupg2_2.0.12.orig.tar.gz
  to pool/main/g/gnupg2/gnupg2_2.0.12.orig.tar.gz
gpgsm_2.0.12-1_amd64.deb
  to pool/main/g/gnupg2/gpgsm_2.0.12-1_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 499569@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Eric Dorland <eric@debian.org> (supplier of updated gnupg2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Sun, 23 Aug 2009 20:48:11 -0400
Source: gnupg2
Binary: gnupg-agent gpgsm gnupg2
Architecture: source amd64
Version: 2.0.12-1
Distribution: unstable
Urgency: low
Maintainer: Eric Dorland <eric@debian.org>
Changed-By: Eric Dorland <eric@debian.org>
Description: 
 gnupg-agent - GNU privacy guard - password agent
 gnupg2     - GNU privacy guard - a free PGP replacement (new v2.x)
 gpgsm      - GNU privacy guard - S/MIME version
Closes: 314068 446494 463270 499569 514587 519375 528734
Changes: 
 gnupg2 (2.0.12-1) unstable; urgency=low
 .
   * New upstream release. (Closes: #499569, #463270, #446494, #314068,
     #519375, #514587)
   * debian/control: Change build dependency on gs to ghoscript, since
     ghoscript has been replaced.
   * debian/compat: Use debhelper v7.
   * debian/control: Update Standards-Version to 3.8.2.
   * debian/control: Use ${misc:Depends}.
   * configure.ac: Override pkgdatadir so that it points to
     /usr/share/gnupg2. (Closes: #528734)
   * debian/rules: No longer need to specify pkgdatadir at make install
     time.
Checksums-Sha1: 
 f4a5c78e93f54bde191989e37fd945dc6ed3748a 1363 gnupg2_2.0.12-1.dsc
 af39fac30404fc74e14cfe01b4f31d2377ceb09e 5395559 gnupg2_2.0.12.orig.tar.gz
 266d424f8f64d38a0bc5624358d2fca680885496 292731 gnupg2_2.0.12-1.diff.gz
 5064adad26de8ead59605818568a67a5ad6125bf 314506 gnupg-agent_2.0.12-1_amd64.deb
 6efa85e9d707e39db579ce1074f3276105add82f 497398 gpgsm_2.0.12-1_amd64.deb
 a0769200addfcf26b630e4217a45f2aa040faef3 2206528 gnupg2_2.0.12-1_amd64.deb
Checksums-Sha256: 
 495c751bf95354648288627d1debad60e5fa7386be69f6108f3dace11ed5b0b4 1363 gnupg2_2.0.12-1.dsc
 cfdaac208836698208bc234d0d14e0630c577a78859924851b53f2f28682f8f5 5395559 gnupg2_2.0.12.orig.tar.gz
 f6bf79899b46ab39e694dba4e811c78f5f5749f35194948c163d4602730c9282 292731 gnupg2_2.0.12-1.diff.gz
 bde6989d48e944b213160349aae55529df98de44182436e0e4aeff0b21223d3f 314506 gnupg-agent_2.0.12-1_amd64.deb
 a5d3bef74af08647542d11c20b207976927fa440a210239dc4a9ce6a8a6c8661 497398 gpgsm_2.0.12-1_amd64.deb
 59cd22178407d7eddd297e6cc45c0320bd8375f8c20e3c65bf677ebf90b9875d 2206528 gnupg2_2.0.12-1_amd64.deb
Files: 
 e7be6d0f63f96a8a5256f4d9f020edb5 1363 utils optional gnupg2_2.0.12-1.dsc
 47484129e46fbc422d33021be78da323 5395559 utils optional gnupg2_2.0.12.orig.tar.gz
 10f627cab531c7487cb880315acb2284 292731 utils optional gnupg2_2.0.12-1.diff.gz
 05bf8c2d9eff9c6ae6dc571e3ddc7752 314506 utils optional gnupg-agent_2.0.12-1_amd64.deb
 cc9c45bedfe158345a8e733e9b2afa21 497398 utils optional gpgsm_2.0.12-1_amd64.deb
 fb99bd87b196956944eb41aa8cdd601d 2206528 utils optional gnupg2_2.0.12-1_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQFKkeksYemOzxbZcMYRAuRuAKCgRs5K4AIM+Zm4DoJiFoIj2TogfACcCEk8
LZyA1GPwEVmYC8NSruDKk94=
=1AEm
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.