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

Incorrect documentation of pivy-tool #199

Closed
anotherbridge opened this issue Nov 23, 2023 · 4 comments
Closed

Incorrect documentation of pivy-tool #199

anotherbridge opened this issue Nov 23, 2023 · 4 comments

Comments

@anotherbridge
Copy link
Contributor

After going through the setup of creating a certificate on a Nitrokey 3 (firmware v1.5.0) described in https://docs.nitrokey.com/nitrokey3/windows/piv I was not able to get a Nitrokey recognized by pivy tool. It is always prompting pivy-tool: no PIV cards/tokens found. Are there any steps missing in the documentation? If not I would like to have the documentation clarified on that usage.
FYI: I tested this on several Linux distributions as well as macOS and got the same result everytime.

Further the documentation states the usage as pivy-tool <operation> [options] while from pivy the correct usage is pivy-tool [options] <operation>.

@sosthene-nitrokey
Copy link
Contributor

Hi!

PIV is currently not considered stable and is therefore only available on the stable releases of the firmware.
To make piv functionality available, you will need to install a test release, marked as test in the name. The latest such firmware release is version 1.5.0-test.20231030.

You can install it with nitropy nk3 update --version v1.5.0-test.20231030.

Note that since these releases are considered unstable, updating the firmware might require reset of the unstable functionality, such as PIV.

This is documented at https://docs.nitrokey.com/nitrokey3/windows/firmware-update#firmware-release-types

@anotherbridge
Copy link
Contributor Author

Thanks a lot @sosthene-nitrokey

Is there already an estimate on when this feature will be available in the stable release?

@daringer
Copy link
Contributor

@jans23
Copy link
Member

jans23 commented Jul 25, 2024

I think the documentation is up to date and thus this issue is solved.

@jans23 jans23 closed this as completed Jul 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants