A command line tool for interacting with Nitrokey devices (GitHub mirror) https://git.ireas.org/mirrors/nitrocli/atom?h=v0.3.1 2020-01-03T21:57:25Z 2020-01-03T21:57:25Z Daniel Mueller deso@posteo.net 2020-01-03T21:57:25Z urn:sha1:6bf2c62147a632f13509ef37942517ae05a421d3 This change bumps the version of the crate to 0.3.1. The following notable changes have been made since 0.3.0: - Added note about interaction with GnuPG to README file - Bumped nitrokey dependency to 0.4.0 - Bumped nitrokey-sys dependency to 3.5.0 - Added lazy_static dependency in version 1.4.0 - Added cfg-if dependency in version 0.1.10 - Added getrandom dependency in version 0.1.13 2020-01-02T16:32:06Z Daniel Mueller deso@posteo.net 2020-01-02T16:32:06Z urn:sha1:fd091b04316db9dc5fafadbd6bdbe60b127408a9 This change finally updates the version of the nitrokey crate that we consume to 0.4.0. Along with that we update rand_core, one of its dependencies, to 0.5.1. Further more we add cfg-if in version 0.1.10 and getrandom in version 0.1.13, both of which are now new (non-development) dependencies. Import subrepo nitrokey/:nitrokey at e81057037e9b4f370b64c0a030a725bc6bdfb870 Import subrepo cfg-if/:cfg-if at 4484a6faf816ff8058088ad857b0c6bb2f4b02b2 Import subrepo getrandom/:getrandom at d661aa7e1b8cc80b47dabe3d2135b3b47d2858af Import subrepo rand/:rand at d877ed528248b52d947e0484364a4e1ae59ca502 2020-01-02T02:15:37Z Daniel Mueller deso@posteo.net 2020-01-02T02:15:37Z urn:sha1:8161cdb26f98e65b39c603ddf7a614cc87c77a1c This change updates two development-only crates that have received upstream updates: - nitrokey-test is updated to 0.3.2 - regex is updated to 1.3.1 2019-12-31T16:47:07Z Daniel Mueller deso@posteo.net 2019-12-31T16:47:07Z urn:sha1:63d4197570e1066805bf76f6bc466fb5eb294036 This change updates the minimum required version of Rust to 1.35.0. The motivation for doing so is at least two fold. First, next we want to bump the nitrokey crate to version 0.4.0 and it requires Rust 1.34.0 as a minimum. Second, and perhaps more importantly, though, in 1.34.0 a clippy lint regressed, breaking our pipeline. That is the reason why we are going to 1.35.0 instead. 2019-12-30T16:42:08Z Daniel Mueller deso@posteo.net 2019-12-30T16:42:08Z urn:sha1:476cbd7238b0a4a0fd842ca5be7706f19c936a12 With Rust 1.40 the unions_with_drop_fields lint has been removed. This change removes it from our list of lints as well. 2019-12-29T17:22:57Z Daniel Mueller deso@posteo.net 2019-12-29T17:22:57Z urn:sha1:4ae7f49555583b0d02fe73354e79243980545b60 This change updates the lazy_static crate version to 1.4.0. Import subrepo lazy-static/:lazy-static at 421669662b35fcb455f2902daed2e20bbbba79b6 2019-12-20T03:21:27Z Daniel Mueller deso@posteo.net 2019-12-20T03:21:27Z urn:sha1:3602aa37413186da0973c069bd0edc701a240dfe Applications accessing the Nitrokey device through libnitrokey apparently lock the device. This lock may not be released in time, causing GnuPG operations performed shortly afterwards to fail (or, the other way around, when accessing the GPG smart card through GnuPG and then using nitrocli, the latter program may fail the interaction). Unfortunately there is nothing we can do directly about this problem on the nitrocli side of things, as the problem seemingly needs to be fixed in the firmware. Hence, with this change we add a note about this problem including a reference to the upstream issue to the README. 2019-12-20T01:44:24Z Daniel Mueller deso@posteo.net 2019-12-20T01:41:52Z urn:sha1:ba79a947fe4e7cc0c6e898bd4a7318a37962fca7 For a while now the program has not only supported Nitrokey Storage but also Nitrokey Pro devices. Back when we added support for the latter we missed updating the program's description inside Cargo.toml. This change takes care of this oversight. 2019-08-13T05:23:33Z Daniel Mueller deso@posteo.net 2019-08-13T05:23:33Z urn:sha1:47ea358ddc1bc37b809f9f5b893a6b099cbb262b This change updates the version of the nitrokey crate that we use to 0.4.0-alpha.3. This version is the supposedly last pre-release before 0.4.0, with no further major anticipated changes. In order to integrate with this new version we have to adjust the way we connect to a Nitrokey device by funneling those connection requests through a global manager object. The rationale behind that step being that the underlying libnitrokey actually cannot handle access of multiple devices at the same time, and so the manager object is used to prevent accidental wrong concurrent usage. Because a device object now effectively keeps a reference to the manager, we need to provide an additional lifetime to that and derived objects. Lastly, the use of a manager is also the reason why the tests had to be adjusted to no longer accept device objects in their signatures, but only the respective model for which to invoke the test. That is required because, as elaborated earlier on, having a device object implies having taken a reference to a manager (in that case owned by nitrokey-test), and that reference clashes with the nitrocli code itself attempting to take the manager. We side step this problem by merely accepting a Model object, which can be passed around independently of the manager itself, meaning that nitrokey-test does not need to hold such a reference while the test is run. Import subrepo nitrokey/:nitrokey at f150d59410eefdec2ae69b2422906a3d1d88aa07 Import subrepo nitrokey-sys/:nitrokey-sys at 8695e2c762807e033a86c8d03974b686d20cdd72 Import subrepo lazy-static/:lazy-static at b4b2b16aaa79dd7548e288455a0dbe4065bf4e1a 2019-08-13T05:07:44Z Daniel Mueller deso@posteo.net 2019-08-13T05:07:44Z urn:sha1:4dc73375e0364aea70b52682b916635b7b75a2eb This change updates the dependency to nitrokey to version 0.4.0-alpha.2. In addition to minor interface changes for the get_*_firmware_version and get_*_retry_count functions, several functions that change the device state now require a mutable handle to the nitrokey. Hence, this patch a number of function signatures to accept mutable device objects. Import subrepo nitrokey/:nitrokey at 34efcfadf1436102e42144f710edabaa2c4b55cd