nitrokey-rs, branch v0.2.0

Release v0.2.0

2018-12-10T14:53:07Z

Provide access to the status of a Nitrokey Storage

2018-12-10T14:48:34Z

This patch adds a `get_status` method to the `Storage` structure. The returned structure `StorageStatus` is based on the structure provided by libnitrokey.

Add a Storage-only example to the DeviceWrapper documentation

2018-12-10T13:36:50Z

As connect() now returns DeviceWrappers of the correct type, this patch adds an example to the DeviceWrapper documentation that shows how to use type conditions, i. e. how to execute a command only for Nitrokey Storage devices.

Fix generic connections (connect()) to return correct device

2018-12-10T13:36:45Z

This patch fixes the generic connect() method to return a DeviceWrapper of the correct type. This is enabled by the NK_get_device_model() method introduced in libnitrokey v3.4.

Always free string pointers returned by libnitrokey

2018-12-10T13:36:40Z

Old libnitrokey versions could return pointers to both statically and dynamically allocated strings for functions that return strings. This has been fixed in libnitrokey commit 7a8550d (included in v3.4). This patch removes the old workaround and always frees the return value of functions returning a string pointer.

Update to nitrokey-sys v3.4.0

2018-12-10T13:36:28Z

Use {} instead of {:?} where possible

2018-06-07T14:07:08Z

Most notably, for command errors, this will print a human-readable error message instead of just the name of the enum.

Implement std::fmt::Display for CommandError

2018-06-07T14:06:50Z

The std::fmt::Display implementation provides a human-readable error message for a CommandError. It is intended to be used in error messages displayed to the user.

Implement easier CString creation

2018-06-07T01:21:57Z

The new get_cstring method in util returns a Result, so mast callers can just use the ? operator to unwrap the result instead of cumbersome unwrapping code.

Use Result<(), CommandError> instead of CommandStatus

2018-06-07T01:03:29Z

The Result enum is more idiomatic and easier to use than our custom CommandStatus enum with the same structure. This is especially true for the try operator ?.