-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document scdaemon reset workaround in readme #164
Comments
robinkrahl
added a commit
to robinkrahl/nitrocli
that referenced
this issue
Apr 24, 2021
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
d-e-s-o
pushed a commit
that referenced
this issue
Apr 24, 2021
We mentioned the libnitrokey/scdaemon incompatibility leading to a hang in 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 #164 [0] Nitrokey/libnitrokey#137
d-e-s-o
added a commit
that referenced
this issue
Apr 24, 2021
libnitrokey issue #164 (Nitrokey/libnitrokey#164) has been closed so the TODO we still have in the code is effectively dangling. Hence, this change removes it.
d-e-s-o
pushed a commit
that referenced
this issue
May 9, 2021
We mentioned the libnitrokey/scdaemon incompatibility leading to a hang in 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 #164 [0] Nitrokey/libnitrokey#137
d-e-s-o
added a commit
that referenced
this issue
May 9, 2021
libnitrokey issue #164 (Nitrokey/libnitrokey#164) has been closed so the TODO we still have in the code is effectively dangling. Hence, this change removes it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We mention Nitrokey/libnitrokey#137 in the readme, but we don’t explain the workaround.
The text was updated successfully, but these errors were encountered: