Skip to content

Commit

Permalink
Document scdaemon workaround in readme
Browse files Browse the repository at this point in the history
We mentioned the libnitrokey/scdaemon incompatibility leading to a
hanging Nitrokey [0] in the readme, but did not explain how to deal with
this issue.  With this patch, we mention that killing scdaemon after
running nitrocli mitigates the problem.  Fixes d-e-s-o#164.

[0] Nitrokey/libnitrokey#137
  • Loading branch information
robinkrahl committed Apr 24, 2021
1 parent 8140504 commit 567b87a
Showing 1 changed file with 4 additions and 2 deletions.
6 changes: 4 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -143,8 +143,10 @@ Known Problems
accessed by `nitrokey-app` ([upstream issue][libnitrokey#32]). To
prevent this problem, quit `nitrokey-app` before using `nitrocli`.
- Applications using the Nitrokey device (such as `nitrocli` or
`nitrokey-app`) cannot easily share access with an instance of GnuPG
running shortly afterwards ([upstream issue][libnitrokey#137]).
`nitrokey-app`) cannot easily share access with an instance of scdaemon/GnuPG
running shortly afterwards ([upstream issue][libnitrokey#137]). As a
workaround, users can kill scdaemon after calling `nitrocli` with
`gpg-connect-agent 'SCD KILLSCD' /bye`.


Public API and Stability
Expand Down

0 comments on commit 567b87a

Please sign in to comment.