A command line tool for interacting with Nitrokey devices (GitHub mirror) https://git.ireas.org/mirrors/nitrocli/atom?h=v0.2.1 2019-01-08T02:00:49Z 2019-01-08T02:00:49Z Daniel Mueller deso@posteo.net 2019-01-08T02:00:49Z urn:sha1:b78c29aad97ddc1913a7fb445c7cc48dc5ae4764 This change bumps the version of the crate to 0.2.1. The following notable changes have been made since 0.2.0: - Added the pws command for accessing the password safe - Added the lock command for locking the Nitrokey device - Adjust release build compile options to optimize binary for size - Bumped nitrokey dependency to 0.2.3 - Bumped rand dependency to 0.6.1 - Added rustc_version version 0.2.3, semver version 0.9.0, and semver-parser version 0.7.0 as indirect dependencies - Bumped cc dependency to 1.0.28 2019-01-07T00:58:32Z Daniel Mueller deso@posteo.net 2019-01-07T00:58:32Z urn:sha1:25258409c09d408c1ccd332ffcdb6ed0e183f54d We have a Result::unwrap in the error path of handling io::Error objects. I have actually seen that fail, masking the original error. We should not unwrap there and in fact we don't have to, as io::Error implements fmt::Display just fine. This may have changed in the past, as the construct we had is much more convoluted than necessary and would only have been written if a direct formatting was not possible. 2019-01-06T04:33:02Z Daniel Mueller deso@posteo.net 2019-01-06T04:33:02Z urn:sha1:9dffcc7b3d119ec444a1e5b4c4e219be9c77a8be By now the nitrocli ebuild has been upstreamed for recent releases and is available in the official Gentoo Portage tree. This change updates the references to the Gentoo ebuild in the README from the custom Github mirror to the official Gentoo Portage tree to move users towards using the official ebuild. 2019-01-05T01:34:17Z Daniel Mueller deso@posteo.net 2019-01-05T01:34:17Z urn:sha1:1a04b3c7ca26ef718c16b7b2e1d51fea29c12301 In order to flush file system level buffers to disk we use the sync function. The way we made this function known to the crate was by explicitly declaring it as extern "C" and linking against libc. However, given that we already (indirectly) depend on libc through the nitrokey crate (and that is unlikely to change) we may as well make libc a direct dependency and invoke the function through the crate. Given that the libc crate is available for a variety of platforms, it seems likely that its approach to interfacing with the system libc library is more portable than our hand rolled version. 2019-01-05T00:42:13Z Daniel Mueller deso@posteo.net 2019-01-05T00:42:13Z urn:sha1:e70143fdb71a99ad160d0bec33d47b4248c0f2ec For a while now the program has supported the Nitrokey Pro device in addition to the Nitrokey Storage. To reflect this change, this patch adjusts the keywords in Cargo.toml to include 'nitrokey-pro' as well. In order to not exceed the crates.io imposed limit, it removes the 'hid' keyword. 2019-01-05T00:30:33Z Daniel Mueller deso@posteo.net 2019-01-05T00:30:33Z urn:sha1:1c765e345abbbb54f8bc533baebc8300685c4d05 A while ago we removed all device specific tests from the project as part of the move to using the nitrokey crate. While adding additional tests is a work in progress, the intention is to have them run solely by issuing 'cargo test'. In any case, this change removes the 'test' target from the Makefile as it is no longer needed, because all tests can run concurrently just fine. 2019-01-03T17:30:35Z Daniel Mueller deso@posteo.net 2019-01-03T17:30:35Z urn:sha1:d2c30bf5a212061c70f5ac2fded8a6519c4a2870 With the recent update of the nitrokey create the nitrokey::CommandError enum has become trivially copyable. Hence, there is no more point in passing a reference to it to the get_error function. To that end, this change adjusts the signature to accept an owned value instead. 2019-01-03T05:14:10Z Daniel Mueller deso@posteo.net 2019-01-03T05:14:10Z urn:sha1:ecf3474223ca3d16a10f12dc2272e3b0ed72c1bb This change updates the nitrokey crate to version 0.2.3. This version bumps the rand crate used to 0.6.1, which in turn requires an additional set of dependencies. Import subrepo nitrokey/:nitrokey at b3e2adc5bb1300441ca74cc7672617c042f3ea31 Import subrepo rand/:rand at 73613ff903512e9503e41cc8ba9eae76269dc598 Import subrepo rustc_version/:rustc_version at 0294f2ba2018bf7be672abd53db351ce5055fa02 Import subrepo semver-parser/:semver-parser at 750da9b11a04125231b1fb293866ca036845acee Import subrepo semver/:semver at 5eb6db94fa03f4d5c64a625a56188f496be47598 2019-01-02T03:07:10Z Daniel Mueller deso@posteo.net 2019-01-02T03:07:10Z urn:sha1:686f61b75055ecb02baf9d9449525ae447a3bed1 The clippy target as executed by the Gitlab CI excludes a bunch of lints when performing an initial run. That is necessary because some of the source code we rely on violates those rules and would cause the target to fail. The problem with the approach taken is that we list all the individual failing lints, which quickly becomes a maintenance burden. As it turns out clippy has the clippy::all meta-lint that subsumes all of the explicitly specified ones and so with this change we use that instead. 2019-01-03T00:41:53Z Daniel Mueller deso@posteo.net 2019-01-03T00:41:53Z urn:sha1:80eefafd3924ff8c8b1bd82d61d12b79b3369012 This change adjusts the README to reflect that we support both Nitrokey Pro and Nitrokey Storage devices with the program.