unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Vagrant Cascadian <vagrant@debian.org>
Cc: 31337@debbugs.gnu.org
Subject: bug#31337: Unable to use gnuk usb smartcard token on GuixSD
Date: Mon, 07 May 2018 12:04:48 +0200	[thread overview]
Message-ID: <87zi1b93y7.fsf@gnu.org> (raw)
In-Reply-To: <87r2mvui1b.fsf@aikidev.net> (Vagrant Cascadian's message of "Tue, 01 May 2018 15:29:04 -0700")

Hi Vagrant,

Vagrant Cascadian <vagrant@debian.org> skribis:

> I've been unable to use my gnuk usb smartcard token with gnupg on
> GuixSD, and it appears this is because scdaemon is built without libusb
> support:
>
>       $ gpg --card-status
>       gpg: selecting openpgp failed: No such device
>       gpg: OpenPGP card not available: No such device
>
> Attached is a patch that gets scdaemon working for me and a gnuk...
>
> Unfortunately, enabling libusb causes one of the tets to hang
> indefinitely:
>
>       PASS: tests/openpgp/decrypt-session-key.scm
>       Checking unwrapping the encryption.
>           > encsig-2-keys-3 encsig-2-keys-4 <
>       PASS: tests/openpgp/decrypt-unwrap-verify.scm
>       Checking signing with the default hash algorithm
>           >
>
> So far, I've only been able to get it to work by disabling the
> tests... so it's obviously not a good idea to enable without further
> troubleshooting.

Did you try attaching strace or gdb to the faulty test to see what’s
going on?

It may be that this test depends on the availability of special hardware
or something like that, in which case we should arrange to skip just
this test.

Thanks for looking into it!

Ludo’.

  parent reply	other threads:[~2018-05-07 10:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-01 22:29 bug#31337: Unable to use gnuk usb smartcard token on GuixSD Vagrant Cascadian
2018-05-02  5:57 ` Nils Gillmann
2018-05-07 10:04 ` Ludovic Courtès [this message]
2018-05-08  5:53 ` Chris Marusich
2018-06-02 21:33   ` Vagrant Cascadian
2021-06-13  8:04     ` Brice Waegeneire
2021-07-04 11:01       ` Brice Waegeneire

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zi1b93y7.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=31337@debbugs.gnu.org \
    --cc=vagrant@debian.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).