A command line tool for interacting with Nitrokey devices (GitHub mirror) https://git.ireas.org/mirrors/nitrocli/atom?h=devel-20210110 2020-12-01T03:50:27Z 2020-12-01T03:50:27Z Daniel Mueller deso@posteo.net 2020-12-01T03:50:27Z urn:sha1:64dc5bcbcc703d72fc57f0675492b13ac7aeaba9 The intra_doc_link_resolution_failure lint has been renamed to broken_intra_doc_links in recent versions of Rust. With this change we update it accordingly in our list of lints to use for the crate. Because our CI tests against the minimum supported Rust version, which does not yet understand the new lint, we configure it to allow unknown lints. 2020-10-12T00:07:08Z Daniel Mueller deso@posteo.net 2020-10-04T16:46:31Z urn:sha1:f65b150049ec9dc5ff2500d7e54c464d530f2e66 With recent changes we are able to execute user-provided extensions through the program. However, discoverability is arguably lacking, because nitrocli provides no insight into what extensions are available to begin with. This patch changes this state of affairs by listing available extensions in the help text. 2020-10-12T00:07:07Z Daniel Mueller deso@posteo.net 2020-08-26T02:04:50Z urn:sha1:8cf63c6790192c30c81294e7a940d470bf061cbf This change introduces support for discovering and executing user-provided extensions to the program. Extensions are useful for allowing users to provide additional functionality on top of the nitrocli proper. Implementation wise we stick to an approach similar to git or cargo subcommands in nature: we search the directories listed in the PATH environment variable for a file that starts with "nitrocli-", followed by the extension name. This file is then executed. It is assumed that the extension recognizes (or at least not prohibits) the following arguments: --nitrocli (providing the path to the nitrocli binary), --model (with the model passed to the main program), and --verbosity (the verbosity level). 2020-09-26T21:01:25Z Daniel Mueller deso@posteo.net 2020-09-26T21:01:25Z urn:sha1:330142e68cac0116babbf2fd64fc9ff0fde132c0 This change reorders and subdivides the Environment section we have in the manual. The first subsection in it is about variables pertaining the program configuration and the second one about those influencing password & PIN entry. Having these dedicated subsections will subsequently allow us to reference them in follow up changes. The reordering is meant to reflect the more general applicability that configuration variables have. 2020-10-11T23:26:54Z Robin Krahl robin.krahl@ireas.org 2020-09-29T17:18:56Z urn:sha1:aaf0286994fcffa8dc81a2569ad70ec6fd7c9b90 This patch renames the options for the config set command: --numlock ==> --num-lock --capslock ==> --caps-lock --scrolllock ==> --scroll-lock --no-numlock ==> --no-num-lock --no-capslock ==> --no-caps-lock --no-scrolllock ==> --no-scroll-lock The original naming was based on a typo in nitrokey-rs (scrollock vs. scrolllock). Also, the typical spelling for the keys is Num Lock, Caps Lock and Scroll Lock, so using a hyphen is a more natural. 2020-10-11T22:02:49Z Robin Krahl robin.krahl@ireas.org 2020-09-29T17:07:05Z urn:sha1:6be92c8425dd5285c16a1722aa95683ea146cf46 This patch removes the unused DeviceModel::as_user_facing_str method. The device model is only used for the argument handling. When printing messages for the user, we always use nitrokey::Model. Its Display implementation already prints the model in an appropriate format. 2020-10-11T22:02:46Z Robin Krahl robin.krahl@ireas.org 2020-09-25T00:09:18Z urn:sha1:23f455ab2e36a019ec62450c5b40949663395963 This patch adds the librem device model for the Librem Key. 2020-10-11T21:58:35Z Robin Krahl robin.krahl@ireas.org 2020-09-25T00:06:00Z urn:sha1:6fce98ec044241abd1d0f54dca307af6cd9f648f This patch updates the nitrokey dependency to version 0.8.0 and applies all breaking changes (Config fields renaming, DeviceWrapper and Model non-exhaustiveness, changed Display implementation for Model). 2020-10-04T13:51:10Z Daniel Mueller deso@posteo.net 2020-10-04T13:51:10Z urn:sha1:dc99d8ffabcd51bc549981998c5d53b1fba789e9 When we switched the default OTP format from hexadecimal to base32 we missed that the manual was providing examples of the otp set command that were implicitly making use of the default format -- leading to a mismatch between what the example is meant to do and what it actually does. This change fixes this oversight in the manual by adjusting the examples accordingly. 2020-09-30T03:31:50Z Daniel Mueller deso@posteo.net 2020-09-30T03:31:50Z urn:sha1:1229dd36306ac43480fcf2bfb91aa47d41ea5e77 When we originally switched over to using anyhow for error handling, we evidently missed to take advantage of its context support in a couple of error paths. The result was that we ended up with rather long winded > result.ok_or_else(|| anyhow::anyhow!(...)) constructs. This change shortens them, making use of the anyhow::Context trait.