-
-
Notifications
You must be signed in to change notification settings - Fork 187
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
Hotp version v1.6 #1684
Hotp version v1.6 #1684
Conversation
Signed-off-by: nestire <[email protected]>
Signed-off-by: nestire <[email protected]>
7c8fb5c
to
ea05b1e
Compare
Ok. Replicating as end user. First step upgrading the nk3 firmwarehttps://github.com/Nitrokey/nitrokey-3-firmware lands to https://docs.nitrokey.com/nitrokey3/ lands to nowhere for clear instructions. Going back to https://github.com/Nitrokey/nitrokey-3-firmware to land at https://github.com/Nitrokey/nitrokey-3-firmware/releases/tag/v1.7.0 to realise 1.7.1 is not official. Ok, info not pointed out from nitrokey-3-firmware to nitropy we expect the user to be advanced and already having updated the firmware before. Nitropyhttps://github.com/Nitrokey/pynitrokey and nitropy don't have the same name. Landing at https://docs.nitrokey.com/nitrokey3/ again. going back to README.md
Nothing tells me how to install pipx
Okok landing at https://docs.nitrokey.com/nitrokey3/linux/firmware-update.html#troubleshooting hmm will update to 1.7.1 but won't be able to downgrade. Okok Landing to https://docs.nitrokey.com/software/nitropy/all-platforms/installation.html I end up having to type all the following for things to work
Okok, crafting the version string to v.1.7.1 I'm under qubesos, so I guess I should know that switching to bootloader will change VID:PID and I have to reassign dongle back to testing qube
I reassign dongle, retry:
Can a guide be drafted so prerequites to testing this PR can replicated from Q4.2.1 from NK3 firmware 1.5.0 that refuses to upgrade to 1.7.1? |
Ok, fine. Default user might want to wipe his dongle to upgrade. I would prefer not to, but this is replication of firmware upgrade here. Let's do it
Hmm. @nestire ? EDIT: attached nitropy logs from latest availabe version applied from above command traces in previous comment. |
Will try the nitrokey app 2 path and open relative issues pointing here as well. Following the white rabbithttps://github.com/Nitrokey/nitrokey-app2 Ok. Flatpak no debian packages. Stil lunder q4.2.1 here. I see macos instructions for pypi. pypi pathlanding on https://pypi.org/project/nitrokeyapp/
okok
Ok instructions made as if I was a developer. Adding untold missing dependencies from instructions: Redoing
Success. Landing under nitrokeyapp2
Ok...
So libxcb-cursor0 is missing. Redoing clean
Same result but graphical and with less details as previous comment |
Hi |
@daringer testing WiP processes including subthread answer at QubesOS/qubes-issues#8953 (comment). Please make sure Nitrokey/nitrokey-documentation#248 can be followed by end users since this PR won't be merged before this happens. |
@daringer you might want to investigate QubesOS/qubes-issues#6330 (comment) |
@nestire I do not see oem-factory-reset being updated to set a secure element PIN to match ADMIN PIN here either for OEM/user cases. Updates at QubesOS/qubes-issues#8953 (comment) down |
This is done by the hotp-verification if no pin is set see here https://github.com/Nitrokey/nitrokey-hotp-verification/blob/e9050e0c914e7a8ffef5d1c82a014e0e2bf79346/src/operations_ccid.c#L105 If there is a pin already set, this likely means the user is using the secret app in the nk3. Because of that we don't wan't to reset this within heads but within nitropy/Nitrokey App 2., So they don't lose passwords and other hotp secrets accidentally. |
perfect so I understand this sub-thread topic is to be followed until fixed: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@daringer please update referred tickets at #1684 (comment) and next comments.
Ideal would be to have packages to deploy under sys-usb and qubes associated templates to not go in such loops of workarounds for not so technical users to follow, aka debian and fedora repositories at least in quebesos testing repositories. |
this is a windows issue so not related here the other issues should be resolved with the fix in Qubes. We working on packages for Qubes/Fedora and for Debian to make this process more user friendly, but this should not block this since this PR will also not break usage of nitrokey3 with an older firmware then 1.7.1 |
Nitrokey/nitrokey-documentation#248 was merged. Retesting doc, will edit this reply
|
@nestire #1684 (comment) ping |
This is needed to get the nitrokey 3 with 1.7.1 firmware to work on heads.
The Error Message is there to make the user aware that resetting the admin pin of the secrets app in the NK 3 Firmware is currently only possible with nitropy and the Nitrokey App 2 and not within heads.
Tested on:
NV41Nitropad : NK3 1.6; NK 1.7.1; NK Storage; NK Pro