From: Pierre Neidhardt <ambrevar@gmail.com>
To: Marius Bakke <mbakke@fastmail.com>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: Nitrokey and udev rules
Date: Wed, 23 May 2018 10:47:22 +0200 [thread overview]
Message-ID: <87efi2ahd1.fsf@gmail.com> (raw)
In-Reply-To: <878t8bg0hp.fsf@fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 842 bytes --]
Marius Bakke <mbakke@fastmail.com> writes:
> As a workaround you can try e.g. 'GROUP+="gpg", MODE=”0660″'.
I tried your suggestion but then `dmesg | grep udevd` rightfully
complained that the "gpg" group did not exist.
Am I supposed to create it?
Anyways, I tried with 'GROUP+="users", MODE=”0666″', but it did not work either.
> I suspect you may also need 'pcscd' which we currently don't have a
> service for.
The Nitrokey is a PGP key I believe. According to Arch Wiki
(https://wiki.archlinux.org/index.php/GnuPG#GnuPG_with_pcscd_.28PCSC_Lite.29),
if it were the issue I should see an error like
> gpg: selecting openpgp failed: ec=6.108
I also tried to install libusb-compat in my operating system package
selection as suggested by Arch Wiki, to no avail.
Any clue? Otherwise I'll ask Nitrokey.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-05-23 8:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 10:53 Nitrokey and udev rules Pierre Neidhardt
2018-05-22 12:41 ` Ricardo Wurmus
2018-05-22 14:30 ` Pierre Neidhardt
2018-05-22 15:42 ` Marius Bakke
2018-05-23 8:47 ` Pierre Neidhardt [this message]
2018-05-23 9:09 ` Pierre Neidhardt
2018-05-23 9:51 ` Pierre Neidhardt
2018-05-24 4:30 ` Mike Gerwitz
2018-05-24 14:04 ` Pierre Neidhardt
2018-05-25 1:44 ` Mike Gerwitz
2018-05-25 5:22 ` Ricardo Wurmus
2018-05-25 13:37 ` Pierre Neidhardt
2018-05-25 14:46 ` Pierre Neidhardt
2018-05-26 1:22 ` Mike Gerwitz
2018-05-26 1:16 ` Mike Gerwitz
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87efi2ahd1.fsf@gmail.com \
--to=ambrevar@gmail.com \
--cc=help-guix@gnu.org \
--cc=mbakke@fastmail.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.