From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#31337: Unable to use gnuk usb smartcard token on GuixSD Date: Mon, 07 May 2018 12:04:48 +0200 Message-ID: <87zi1b93y7.fsf@gnu.org> References: <87r2mvui1b.fsf@aikidev.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47213) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fFd1z-0006Pa-Hw for bug-guix@gnu.org; Mon, 07 May 2018 06:06:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fFd1u-0002W4-Iz for bug-guix@gnu.org; Mon, 07 May 2018 06:06:07 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:44104) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fFd1u-0002Vc-GB for bug-guix@gnu.org; Mon, 07 May 2018 06:06:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fFd1u-0000o0-5q for bug-guix@gnu.org; Mon, 07 May 2018 06:06:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87r2mvui1b.fsf@aikidev.net> (Vagrant Cascadian's message of "Tue, 01 May 2018 15:29:04 -0700") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Vagrant Cascadian Cc: 31337@debbugs.gnu.org Hi Vagrant, Vagrant Cascadian 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=E2=80=99s 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=E2=80=99.