Package: gnupg2
Version: 2.0.14-2
Severity: normal

With Smartcard, signing with SHA256 is not possible in current gpg2 in
Debian.  It is already fixed in trunk, please consider to include
the fix for Debian.

Message in list:
http://lists.gnupg.org/pipermail/gnupg-devel/2010-November/025819.html

Fix by Gentoo guy:
http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/app-crypt/gnupg/files/gnupg-2.0.16-opengpgv2-sha2.patch?revision=1.1&view=markup

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages gnupg2 depends on:
ii  dpkg                    1.15.8.5         Debian package management system
ii  gnupg-agent             2.0.14-2         GNU privacy guard - password agent
ii  install-info            4.13a.dfsg.1-6   Manage installed documentation in 
ii  libbz2-1.0              1.0.5-6          high-quality block-sorting file co
ii  libc6                   2.11.2-7         Embedded GNU C Library: Shared lib
ii  libcurl3-gnutls         7.21.2-1         Multi-protocol file transfer libra
ii  libgcrypt11             1.4.5-2          LGPL Crypto library - runtime libr
ii  libgpg-error0           1.6-1            library for common error values an
ii  libksba8                1.0.7-2          X.509 and CMS support library
ii  libreadline6            6.1-3            GNU readline and history libraries
ii  zlib1g                  1:1.2.3.4.dfsg-3 compression library - runtime

Versions of packages gnupg2 recommends:
ii  libldap-2.4-2                 2.4.23-6   OpenLDAP libraries

Versions of packages gnupg2 suggests:
pn  gnupg-doc                     <none>     (no description available)
pn  xloadimage                    <none>     (no description available)

-- no debconf information



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to