From: Vagrant Cascadian <vagrant@debian.org>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: 31337@debbugs.gnu.org
Subject: bug#31337: Unable to use gnuk usb smartcard token on GuixSD
Date: Sat, 02 Jun 2018 14:33:28 -0700 [thread overview]
Message-ID: <877engrhzr.fsf@aikidev.net> (raw)
In-Reply-To: <87efimpuam.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]
On 2018-05-07, Chris Marusich wrote:
> Vagrant Cascadian <vagrant@debian.org> writes:
>
>> Another option might be to use pcsc-lite and ccid, but I had even less
>> luck getting that to work.
>
> When you tried that, did you enable the USB drivers by creating a
> symlink as described here?
>
> https://lists.gnu.org/archive/html/guix-devel/2016-10/msg01433.html
With the symlink:
lrwxrwxrwx 1 root root 41 Jun 2 06:31 /var/lib/pcsc/drivers -> /home/vagrant/.guix-profile/pcsc/drivers/
Then I tried to run:
pcscd --debug --foreground
00000000 pcscdaemon.c:347:main() pcscd set to foreground with debug send to stdout
00000077 pcscdaemon.c:623:main() cannot create /var/run/pcscd: Permission denied
Running as root appears to have worked:
sudo -E --debug --foreground pcscd
Then as a user, "gpg --card-status" works. Haven't tried any other
functionality yet, but that's a good start.
So this seems like a somewhat complicated workaround, and making a
proper pcscd service would reduce the complication significantly. It
would obviously be slightly preferable to me for gnupg to support
smartcards out of the box. :)
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-06-02 21:34 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
2018-05-08 5:53 ` Chris Marusich
2018-06-02 21:33 ` Vagrant Cascadian [this message]
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=877engrhzr.fsf@aikidev.net \
--to=vagrant@debian.org \
--cc=31337@debbugs.gnu.org \
--cc=cmmarusich@gmail.com \
/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).