nitrokey-rs/src, branch v0.7.0

Ensure Error trait implementations

2020-07-08T21:03:02Z

The anyhow crate requires that error types are error::Error, Send, Sync and 'static. This patch implements a simple static assertion that our Error type implements these traits.

Remove Error::RandError variant

2020-07-08T21:02:56Z

Since we update rand_os to version 0.2 in commit 6c138eaa850c745b97b7e48a201db0cbaad8e1e0, the random number generation can no longer fail. Therefore the Error::RandError variant is no longer needed. As we did not want to break the public API, we still kept the RandError variant. This patch removes the RandError variant for good.

Remove sync::PoisonError from Error::PoisonError

2020-07-08T21:02:49Z

Previously, the Error::PoisonError contained the sync::PoisonError that caused the error. This is problematic as sync::PoisonError does not implement Send, making it impossible to use the Error enum with the anyhow crate. At the same time, storing the sync::PoisonError is not very useful. If a user wants to access the poisoned lock, they can call the force_take function. Therefore we remove the sync::PoisonError value from the Error:: PoisonError variant. This also allows us to simplify the From> and From> implementations as we no longer need to know the type of the mutex that caused the error. For more information, see this thread: https://lists.sr.ht/~ireas/nitrokey-rs-dev/%3C68ed0f3f-d98f-63bc-04d2-81b6d6cde560%40posteo.net%3E

Use find(…) instead of skip_while(…).next()

2020-07-08T21:02:43Z

This patch replaces calls to skip_while(…).next() for an iter::Iterator with a call to find(…), as suggested by clippy.

Remove unused imports

2020-07-08T21:02:34Z

Refactor string handling in util

2020-02-03T10:31:21Z

The util module provides helper methods to deal with the C strings returned by libnitrokey. The current implementation has to problems: - It causes unnecessary allocations if we only want to look at the string, for example in get_serial_number. - If the conversion from a CStr to a String fails, the string pointer is not freed. Therefore this patch introduces the run_with_str function that executes a function with the string returned by libnitrokey and then makes sure that the pointer is freed correctly.

Represent serial numbers using SerialNumber struct

2020-02-03T10:30:57Z

In a previous commit, we changed the serial number representation from a string to an integer. This made it easier to compare serial numbers, but also introduced new problems: - Serial numbers should be formatted consistently, for example as "{:#010x}". It is hard to ensure this for an integer value. - The format of the serial number may be subject to change. Users should not rely too much on the u32 representation. Therefore we introduce a new SerialNumber struct that represents a serial number. Currently it only stores a u32 value. The following traits and functions can be used to access its value: - FromStr for string parsing - ToString/Display for string formatting - as_u32 to access the underlying integer value

Use NK_get_status to implement Device::get_config

2020-02-03T09:22:13Z

libnitrokey’s NK_read_config function returns a pointer to an array that has been allocated using new[]. We would have to delete this pointer using delete[], but we only have access to free. Therefore this patch modifies the Device::get_config function to call NK_get_status instead of NK_read_config. This also makes the code more safe as we get the data as a struct instead of an array. It does not add much overhead as NK_read_config also executes the GET_STATUS command on the Nitrokey device.

Implement From<&NK_status> for RawConfig

2020-02-03T09:19:21Z

This makes it easier to parse only the config part of the NK_status struct and avoids code duplication in the upcoming get_config refactoring.

Merge branch 'hotfix-0.5.2' into next

2020-01-28T20:23:13Z