A command line tool for interacting with Nitrokey devices (GitHub mirror) https://git.ireas.org/mirrors/nitrocli/atom?h=v0.2.4 2019-06-01T18:57:17Z 2019-06-01T18:57:17Z Daniel Mueller deso@posteo.net 2019-06-01T18:57:17Z urn:sha1:a7b63f8a0570f0c798af7eaadfaf6f4da14cd54c This change bumps the version of the crate to 0.2.4. The following notable changes have been made since 0.2.3: - Added the reset command to perform a factory reset - Added the -V/--version option to print the program's version - Check the status of a PWS slot before accessing it in pws get - Added NITROCLI_NO_CACHE environment variable to bypass caching of secrets - Clear cached PIN entry as part of pin set command to prevent spurious authentication failures - Bumped libc dependency to 0.2.57 - Bumped cc dependency to 1.0.37 2019-06-01T18:46:58Z Daniel Mueller deso@posteo.net 2019-06-01T18:46:58Z urn:sha1:61f2baa0af6b2a54e0c109e5f73c8ff25f9f2ca6 This change updates the libc crate to version 0.2.57. Import subrepo libc/:libc at cdc48ea36d8d2890dba38e8f779001e6855339a2 2019-06-01T18:19:08Z Daniel Mueller deso@posteo.net 2019-06-01T18:19:08Z urn:sha1:7c880699bb9a49037c09b1be990e677a1857af7a When a PIN is changed using the pin set command, the last action is to confirm the operation with the previously used PIN. This step will cause this PIN, which is now stale and no longer valid, to be cached, which in turn can cause follow up command using the same PIN type to use this wrong cached entry for authentication. To fix this problem, this change explicitly clear the PIN entry from the cache after the PIN has been changed. 2019-05-27T15:32:06Z Daniel Mueller deso@posteo.net 2019-05-27T05:11:36Z urn:sha1:a57449dcd2abe1fa5dae195470fccc9a9a398e04 So far we have cached secrets in gpg-agent(1) whenever that made sense to do (i.e., for the two PINs in most contexts but not for passwords). While there is reason to believe that such caching is desired by the majority of users, not everybody has a use for it. To give users an opportunity to opt out of such caching, this change introduces a new environment variable, NITROCLI_NO_CACHE, that, when present in the environment, instructs the program to bypass the cache for all operations that require a secret and to instead inquire such secrets each time they are needed. 2019-05-27T15:16:27Z Daniel Mueller deso@posteo.net 2019-05-27T15:16:27Z urn:sha1:c01bbbf186cd88f9e1b3c3eda0459635bed209b4 The input to the Enum macro is supposed to resemble the definition of an enum in Rust code. When manually defining an enum (or a struct for that matter), we typically terminate all branches with a comma, and don't just omit that on the last line. To mirror this behavior, this change adjusts the Enum macro to accept (and in fact, require) a comma-terminated last line as well, as opposed to not accepting it as had been the case so far. 2019-05-25T01:08:42Z Daniel Mueller deso@posteo.net 2019-05-25T01:08:42Z urn:sha1:b637d5284c6117da3bfeb471da7c62e53a632621 This change updates the cc crate to version 1.0.37. Import subrepo cc/:cc at cbf6d2f1312b6be22a7a363cf5c2a02acabc531f 2019-05-25T01:07:22Z Daniel Mueller deso@posteo.net 2019-05-25T01:07:22Z urn:sha1:82cf43dd887801b8b22b8aae8c02854d921915d5 This change updates the libc crate to version 0.2.55. Import subrepo libc/:libc at caf17a0641d29dc624621177f5756804dd180c13 2019-05-25T00:58:37Z Daniel Mueller deso@posteo.net 2019-05-25T00:58:37Z urn:sha1:06722702ea35434189d7de2b13a00209b2ebbd6d Macros typically should reference types by their full path and not assume that they are in scope wherever the macro is expanded. We did missed one spot where AsRef was not fully qualified in the Enum macro. While that is not much of an issue here (and there may be more occurrences, e.g., in the auto derives) lets fix that up for the sake of consistency. 2019-05-25T00:39:14Z Daniel Mueller deso@posteo.net 2019-05-25T00:39:14Z urn:sha1:5383aa73b339e6a53ff027ee6012a3428f67466a With Rust 1.35 we get compile errors due to doc comments that are added to macro invocations but not actually included in the expanded output. The rustc wrongly assumes that we want to document the resulting code and not just provide details about the invocation itself. This change explicitly allows for those cases. Alternatively we could have "downgraded" the doc comments to normal comments or removed them altogether. There is little difference between those alternatives. 2019-02-18T03:50:52Z Robin Krahl robin.krahl@ireas.org 2019-02-17T13:34:02Z urn:sha1:4625be03bbebe74f5efa93a37f287e7911fbbbb4 This change adds a test case for the -V/--version option to the suite of tests.