<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/nitrocli, branch v0.2.3</title>
<subtitle>A command line tool for interacting with Nitrokey devices (GitHub mirror)
</subtitle>
<id>https://git.ireas.org/mirrors/nitrocli/atom?h=v0.2.3</id>
<link rel='self' href='https://git.ireas.org/mirrors/nitrocli/atom?h=v0.2.3'/>
<link rel='alternate' type='text/html' href='https://git.ireas.org/mirrors/nitrocli/'/>
<updated>2019-01-27T05:49:01Z</updated>
<entry>
<title>Bump version to 0.2.3</title>
<updated>2019-01-27T05:49:01Z</updated>
<author>
<name>Daniel Mueller</name>
<email>deso@posteo.net</email>
</author>
<published>2019-01-27T05:49:01Z</published>
<link rel='alternate' type='text/html' href='https://git.ireas.org/mirrors/nitrocli/commit/?id=eabca4c9612ae24911cca2ea1917f5c0fb2df9e9'/>
<id>urn:sha1:eabca4c9612ae24911cca2ea1917f5c0fb2df9e9</id>
<content type='text'>
This change bumps the version of the crate to 0.2.3. The following
notable changes have been made since 0.2.2:
- Added the storage hidden subcommand for working with hidden volumes
- Store cached PINs on a per-device basis to better support multi-device
  scenarios
- Further decreased binary size by using system allocator
- Bumped nitrokey dependency to 0.3.4
  - Bumped rand dependency to 0.6.4
  - Removed rustc_version, semver, and semver-parser dependencies
- Bumped nitrokey-sys dependency to 3.4.3
- Bumped libc dependency to 0.2.47
</content>
</entry>
<entry>
<title>Remove no longer used duplicate_associated_type_bindings lint</title>
<updated>2019-01-27T05:55:39Z</updated>
<author>
<name>Daniel Mueller</name>
<email>deso@posteo.net</email>
</author>
<published>2019-01-27T05:55:39Z</published>
<link rel='alternate' type='text/html' href='https://git.ireas.org/mirrors/nitrocli/commit/?id=65ae7854a479e6d57b0f6c8603065d768032ffae'/>
<id>urn:sha1:65ae7854a479e6d57b0f6c8603065d768032ffae</id>
<content type='text'>
The duplicate_associated_type_bindings lint seems to have been removed
with the Rust 1.32 release.
This change removes the lint from the program to prevent the newly
introduced warning from being emitted.
</content>
</entry>
<entry>
<title>Document problems in conjunction with nitrokey-app</title>
<updated>2019-01-27T07:10:08Z</updated>
<author>
<name>Robin Krahl</name>
<email>robin.krahl@ireas.org</email>
</author>
<published>2019-01-24T19:56:26Z</published>
<link rel='alternate' type='text/html' href='https://git.ireas.org/mirrors/nitrocli/commit/?id=3f4b606513386ad8c8d52ef9e3874a7b19bd56cd'/>
<id>urn:sha1:3f4b606513386ad8c8d52ef9e3874a7b19bd56cd</id>
<content type='text'>
If nitrokey-app is running, the device it connected to cannot be
detected by other applications. This patch adds this issue to the list
of known problems in the README.
</content>
</entry>
<entry>
<title>Exclude CI scripts and rustmft config</title>
<updated>2019-01-27T07:09:12Z</updated>
<author>
<name>Robin Krahl</name>
<email>robin.krahl@ireas.org</email>
</author>
<published>2019-01-23T18:46:15Z</published>
<link rel='alternate' type='text/html' href='https://git.ireas.org/mirrors/nitrocli/commit/?id=aae8315ea3986b40844959c4ec3d7734b124ddac'/>
<id>urn:sha1:aae8315ea3986b40844959c4ec3d7734b124ddac</id>
<content type='text'>
The CI scripts and the rustfmt configuration are only needed when
developing. There is no point in distributing them in the package
published on crates.io, so we exclude them from packaging using the
exclude setting in Cargo.toml.
</content>
</entry>
<entry>
<title>Update libc crate to 0.2.47</title>
<updated>2019-01-23T04:16:05Z</updated>
<author>
<name>Daniel Mueller</name>
<email>deso@posteo.net</email>
</author>
<published>2019-01-23T04:16:05Z</published>
<link rel='alternate' type='text/html' href='https://git.ireas.org/mirrors/nitrocli/commit/?id=4fcdf2022df38b37365ee5d948005ac08a1f1a83'/>
<id>urn:sha1:4fcdf2022df38b37365ee5d948005ac08a1f1a83</id>
<content type='text'>
This change updates the libc crate to version 0.2.47.

Import subrepo libc/:libc at ce1dfcbf81bd74662b5cd02a9214818a0bfbbffa
</content>
</entry>
<entry>
<title>Update nitrokey crate to 0.3.4</title>
<updated>2019-01-23T04:13:42Z</updated>
<author>
<name>Daniel Mueller</name>
<email>deso@posteo.net</email>
</author>
<published>2019-01-23T04:13:42Z</published>
<link rel='alternate' type='text/html' href='https://git.ireas.org/mirrors/nitrocli/commit/?id=8b2d8818b26e7084cad240c48fd9ce7fc2519012'/>
<id>urn:sha1:8b2d8818b26e7084cad240c48fd9ce7fc2519012</id>
<content type='text'>
This change updates the nitrokey crate to version 0.3.4.

Import subrepo nitrokey/:nitrokey at 41cdc1f7091a3c442241dbb2379c50dbcc7e9c5f
</content>
</entry>
<entry>
<title>Add tests for the lock command</title>
<updated>2019-01-20T22:52:00Z</updated>
<author>
<name>Daniel Mueller</name>
<email>deso@posteo.net</email>
</author>
<published>2019-01-20T22:52:00Z</published>
<link rel='alternate' type='text/html' href='https://git.ireas.org/mirrors/nitrocli/commit/?id=1c6df6757c1ca4972e298011c9548c34051fa887'/>
<id>urn:sha1:1c6df6757c1ca4972e298011c9548c34051fa887</id>
<content type='text'>
This change adds tests for the lock command. For the Nitrokey Pro we
cannot test too much because the only side-effect is that the password
safe is closed and it will be opened automatically again by virtue of
our non-interactive testing methodology.
For Storage devices we verify that the encrypted volume is closed, which
is a documented side-effect.
</content>
</entry>
<entry>
<title>Document hidden volumes in the README and the manual page</title>
<updated>2019-01-20T22:04:50Z</updated>
<author>
<name>Daniel Mueller</name>
<email>deso@posteo.net</email>
</author>
<published>2019-01-20T22:04:50Z</published>
<link rel='alternate' type='text/html' href='https://git.ireas.org/mirrors/nitrocli/commit/?id=8b72cb852a8da420d6d64f83aa0cbf256f36dd68'/>
<id>urn:sha1:8b72cb852a8da420d6d64f83aa0cbf256f36dd68</id>
<content type='text'>
This change updates the README and the man page with documentation about
hidden volumes in general and the storage hidden subcommand in
particular.
</content>
</entry>
<entry>
<title>Add test for storage hidden subcommand</title>
<updated>2019-01-20T21:56:48Z</updated>
<author>
<name>Daniel Mueller</name>
<email>deso@posteo.net</email>
</author>
<published>2019-01-20T21:56:48Z</published>
<link rel='alternate' type='text/html' href='https://git.ireas.org/mirrors/nitrocli/commit/?id=37f7800766fe12af43d0cdba13aea9545cbe7755'/>
<id>urn:sha1:37f7800766fe12af43d0cdba13aea9545cbe7755</id>
<content type='text'>
This change adds a test for the creation, opening, and closing of a
hidden subvolume. In order to support that in a non-interactive fashion,
we introduce and honor the NITROCLI_PASSWORD environment variable, that
prevents an interactive password query.
</content>
</entry>
<entry>
<title>Implement storage hidden subcommand</title>
<updated>2019-01-20T17:26:11Z</updated>
<author>
<name>Daniel Mueller</name>
<email>deso@posteo.net</email>
</author>
<published>2019-01-20T17:26:11Z</published>
<link rel='alternate' type='text/html' href='https://git.ireas.org/mirrors/nitrocli/commit/?id=c3f1761ae147e562ec3565c7ba8a9cb1834759c2'/>
<id>urn:sha1:c3f1761ae147e562ec3565c7ba8a9cb1834759c2</id>
<content type='text'>
With this change we implement the storage hidden subcommand. We support
creation, opening, and closing of hidden volumes.
Note that the opening of a hidden volume automatically closes any opened
encrypted volumes and vice versa. To that end, we force file system
level caches to disk even from the storage open and storage hidden open
commands.
</content>
</entry>
</feed>
