A command line tool for interacting with Nitrokey devices (GitHub mirror) https://git.ireas.org/mirrors/nitrocli/atom?h=v0.2.0 2019-01-02T01:21:10Z 2019-01-02T01:21:10Z Daniel Mueller deso@posteo.net 2019-01-02T01:21:10Z urn:sha1:696d9fb4164c2c92fa614030c18a4216e7bd4c13 This change bumps the version of the crate to 0.2.0. The following notable changes have been made since 0.1.3: - Use the nitrokey crate for the 'open', 'close', and 'status' commands instead of directly communicating with the Nitrokey device - Added nitrokey version 0.2.1 as a direct dependency and nitrokey-sys version 3.4.1 as well as rand version 0.4.3 as indirect dependencies - Removed the hid, hidapi-sys and pkg-config dependencies - Added the 'otp' command for working with one-time passwords - Added the 'config' command for reading and writing the device configuration - Added the 'pin' command for managing PINs - Renamed the 'clear' command to 'pin clear' - Moved 'open' and 'close' commands as subcommands into newly introduced 'storage' command - Moved printing of storage related information from 'status' command into new 'storage status' subcommand - Made 'status' command work with Nitrokey Pro devices - Enabled CI pipeline comprising code style conformance checks, linting, and building of the project - Added badges indicating pipeline status, current crates.io published version of the crate, and minimum version of rustc required - Fixed wrong messages in the pinentry dialog that were caused by unescaped spaces in a string - Use the argparse crate to parse the command-line arguments - Added argparse dependency in version 0.2.2 2019-01-01T23:10:40Z Daniel Mueller deso@posteo.net 2019-01-01T23:10:40Z urn:sha1:a98e417c3373a91fc12df8e483222f67dfac5335 This change adds a new file, CONTRIBUTING.md, that details some generally applicable rules for the contribution to this project. It also links this file from the README. 2019-01-01T23:30:37Z Daniel Mueller deso@posteo.net 2019-01-01T23:30:37Z urn:sha1:d50039f758cc5520b30a0ca65c8d8f77cef949cd This change makes the following set of changes to the installation sections: - Note that Rust and Cargo are implicit dependencies - Remove the notice about the hid crate being required from the "From Source" section as that is no longer a requirement with the switch to using the nitrokey crate - Mention that from source compilation should happen from the nitrocli/ subfolder 2019-01-01T20:17:56Z Daniel Mueller deso@posteo.net 2019-01-01T20:17:56Z urn:sha1:837e378f5512abbd71450d169c249415bfaa173b This change reorders the individual ways to install the program in order of preference. If possible, the user most likely wants to use a distribution's package over installation from crates.io or from source. 2019-01-01T20:16:41Z Daniel Mueller deso@posteo.net 2019-01-01T20:16:41Z urn:sha1:fce2290bcfe633fede393c618bf033752a642bbf This change adds a new section detailing the project's license to the README. Having such a section seems to be relatively common practice among projects. 2019-01-01T20:05:21Z Daniel Mueller deso@posteo.net 2019-01-01T20:05:21Z urn:sha1:8a8d8819d07883db410ba72801ff3023d152be34 This change removes the note about firmware version 0.47 being the minimum required. The note is outdated, because with the switch to using the nitrokey crate and with it libnitrokey we no longer have such a requirement as the CRC check we performed that caused incompatibilities with earlier versions does not exist in libnitrokey (see issue Nitrokey/libnitrokey issue #134). 2019-01-01T19:37:44Z Daniel Mueller deso@posteo.net 2019-01-01T19:37:44Z urn:sha1:e77650547cf2ab410fd6fe16fc5e86cf1b0772d9 This change adds a new target to the Makefile that can be used for generating a PDF version of the man page. It also checks in the generated file and links to it from the README. We have also experimented with creation of an HTML version, but at least the groff generated file is not very visually pleasing and also cannot be linked to directly from Github. Github wants to prevent hosting of web pages directly like this in repositories and instead promote their Github Pages solution for that purpose. To that end they deliver content with a Content-Type representing plain text which causes HTML to not be rendered. PDF content, however, is rendered in-line and looks reasonable at that. 2019-01-02T01:14:58Z Robin Krahl robin.krahl@ireas.org 2018-12-30T17:32:45Z urn:sha1:cc3aa7f14eaec746e6718ef155a59e10c67a03fb This change implements the pin set command which can be used to change a Nitrokey's user or admin PIN. 2019-01-02T01:14:54Z Robin Krahl robin.krahl@ireas.org 2018-12-30T17:39:31Z urn:sha1:fc4a8e12af694a40fe17bcebddd9e4617075400f This patch implements the pin unblock command that unblocks and resets the user PIN. The name unblock is chosen over libnitrokey's unlock to be consistent with the GnuPG terminology and to avoid confusion with the unrelated lock command. 2019-01-02T01:14:51Z Robin Krahl robin.krahl@ireas.org 2018-12-31T18:10:40Z urn:sha1:8a59f307a2e0b9fa398ac200da44d8e5725150a7 We have functionality for changing the Nitrokey's user & admin PINs as well as for resetting the user PIN coming up. With the prospect of this new functionality arriving, it makes sense to introduce a new top-level command for the sole purpose of PIN management. This change introduces such a command, pin, and moves the existing clear command for clearing the PIN cache into it.