From: Pierre Neidhardt <ambrevar@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: Nitrokey and udev rules
Date: Fri, 25 May 2018 16:46:57 +0200 [thread overview]
Message-ID: <87tvqvhk9i.fsf@gmail.com> (raw)
In-Reply-To: <87vabbhn4r.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1416 bytes --]
Different issue, but I have a few problems with `gpg --card-edit`:
1. I can't seem to be able to change the PIN with any pinentry but
pinentry-gtk-2:
- With pinentry-emacs:
> Error changing the PIN: No pinentry
- With pinentry-tty:
> Error changing the PIN: End of file
- With pinentry-curses:
> Error changing the PIN: No such file or directory
2. After transfering my encryption key and my authentication key, `gpg
--card-edit` segfauls:
--8<---------------cut here---------------start------------->8---
> gpg --card-edit
Reader ...........: Nitrokey Nitrokey Start (FSIJ-1.2.6-67143146) 00 00
Application ID ...: D276000124010200FFFE671431460000
Version ..........: 2.0
Manufacturer .....: unmanaged S/N range
Serial number ....: 67143146
Name of cardholder: [not set]
Language prefs ...: [not set]
Sex ..............: unspecified
URL of public key : [not set]
Login data .......: [not set]
Signature PIN ....: forced
Key attributes ...: rsa2048 rsa2048 rsa2048
Max. PIN lengths .: 127 127 127
PIN retry counter : 3 3 3
Signature counter : 0
Signature key ....: [none]
Encryption key....: XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX
created ....: 2015-09-26 19:12:48
keygrip ....:
gpg: signal Segmentation fault caught ... exiting
segmentation fault
--8<---------------cut here---------------end--------------->8---
gpg's fault?
--
Pierre Neidhardt
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-05-25 14: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
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 [this message]
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
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=87tvqvhk9i.fsf@gmail.com \
--to=ambrevar@gmail.com \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
/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).