Package: gnupg
Version: 1.4.3-2
Severity: normal

I'm roughly following http://fsfe.org/en/card/howto/subkey_howto to add
subkeys to my key for use with the OpenPGP card. After doing gpg
--edit-key, I succesfully generated an authentication key, but for the
signature key gpg segfaults.

(The last part of that:)

    Admin PIN
    gpg: please wait while key is being generated ...
    gpg: key generation completed (20 seconds)

    gpg: Segmentation fault caught ... exiting

The Signature key field on the card _is_ updated, but my main key has
not been modified. This happens every time I try to add a signature key,
either using pcscd or the builtin ccid driver. The card reader is an
SCR335.

A backtrace from gdb isn't very informative:

    #0  0x08094d77 in ?? ()
    #1  0x00000000 in ?? ()

I'm going to try a newer version of gpg, also with a cardman4040 for a
card reader, and see if that changes anything.

If there is any other information I can provide, please let me know.
Wouter van Heyst

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17
Locale: LANG=en_GB.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)

Versions of packages gnupg depends on:
ii  libbz2-1.0                  1.0.3-3      high-quality block-sorting file co
ii  libc6                       2.3.6-16     GNU C Library: Shared libraries
ii  libldap2                    2.1.30-13+b1 OpenLDAP libraries
ii  libreadline5                5.1-7        GNU readline and history libraries
ii  libusb-0.1-4                2:0.1.12-2   userspace USB programming library
ii  makedev                     2.3.1-82     creates device files in /dev
ii  zlib1g                      1:1.2.3-13   compression library - runtime

gnupg recommends no packages.

-- no debconf information


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

Reply via email to