From: Mike Gerwitz <mtg@gnu.org>
To: Pierre Neidhardt <ambrevar@gmail.com>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: Nitrokey and udev rules
Date: Fri, 25 May 2018 21:22:39 -0400 [thread overview]
Message-ID: <87r2lzgqhs.fsf@gnu.org> (raw)
In-Reply-To: <87tvqvhk9i.fsf@gmail.com> (Pierre Neidhardt's message of "Fri, 25 May 2018 16:46:57 +0200")
[-- Attachment #1: Type: text/plain, Size: 699 bytes --]
On Fri, May 25, 2018 at 16:46:57 +0200, Pierre Neidhardt wrote:
> 1. I can't seem to be able to change the PIN with any pinentry but
> pinentry-gtk-2:
I have this in my ~/.gnupg/gpg-agent.conf:
pinentry-program /run/current-system/profile/bin/pinentry
Maybe you can try something like that?
> 2. After transfering my encryption key and my authentication key, `gpg
> --card-edit` segfauls:
I haven't experienced segfaults so I can't provide any insight
there. Maybe attaching a debugger can provide some insight.
--
Mike Gerwitz
Free Software Hacker+Activist | GNU Maintainer & Volunteer
GPG: D6E9 B930 028A 6C38 F43B 2388 FEF6 3574 5E6F 6D05
https://mikegerwitz.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2018-05-26 1:22 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
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 [this message]
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
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=87r2lzgqhs.fsf@gnu.org \
--to=mtg@gnu.org \
--cc=ambrevar@gmail.com \
--cc=help-guix@gnu.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.
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).