Skip to content
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 HMAC-SHA1 Challenge Response use with NK3 #284

Open
szszszsz opened this issue Jun 6, 2023 · 3 comments
Open

Document HMAC-SHA1 Challenge Response use with NK3 #284

szszszsz opened this issue Jun 6, 2023 · 3 comments
Labels
app:secrets documentation Improvements or additions to documentation

Comments

@szszszsz
Copy link
Member

szszszsz commented Jun 6, 2023

Make sure HMAC-SHA1 Challenge Response use with NK3 is properly documented.
Recommend FIDO2 HMAC challenge-response use where possible.

Details: #281

@szszszsz szszszsz added documentation Improvements or additions to documentation app:secrets labels Jun 6, 2023
@merryswiftoctopus
Copy link

Hi, I have been able to set up my NitroKey 3A for my Keepass vault; However, I do not quite understand: Is there a way to protect this secret with a PIN? Because now the key just needs to be plugged in, no further authentication required.

@ChristianTackeGSI
Copy link

I never tried it. (I am actually hoping for some fido2-with-pin thing becoming an alternative to the normal password.)

I guess, the idea is that you use it as a second factor in addition to the knowledge of the main keepass password. So you still need to know something (enter password into your keepass) and own something (insert the nitrokey).

@daringer
Copy link
Collaborator

daringer commented Jan 2, 2024

currently this is not possible and @ChristianTackeGSI explains the overall concepts precisely... nevertheless it's still a valid request, which is tracked here: Nitrokey/pynitrokey#487

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
app:secrets documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

4 participants