nitrokey-rs/tests, branch v0.3.1

Add the connect_model function

2019-01-06T23:29:52Z

This patch adds the global connect_model function that can be used to connect to a Nitrokey device of a given model. Contrary to Pro::connect and Storage::connect, the model does not have to be set at compile time.

Add support for the hidden volumes on a Nitrokey Storage

2019-01-06T22:59:54Z

This patch introduces the methods enable_hidden_volume, disable_hidden_volume and create_hidden_volume for the Storage struct to support the hidden volumes on the Nitrokey Storage. The enable and create methods require that the encrypted storage has been enabled. Contrary to authentication and password safe access, we do not enforce this requirement in the API as file system operations could have unwanted side effects and should not performed implicitly.

Fix example for GenerateOtp::get_totp_code

2019-01-05T09:53:25Z

Prefer assert_eq over is_ok() checks

2019-01-05T09:28:49Z

We experienced various problems running the tests and while they may or may not be caused by local setup issues, it is helpful to have more information than just an indication that an assertion (true/false) was violated. To that end, this change adjusts some of the assert!(().is_ok()) to compare against Ok(()) instead. This way, if the result is not the Ok variant, the error code will get printed.

Adjust PWS tests to use nitrokey-test crate

2019-01-05T09:28:43Z

This change adjusts the PWS tests to use the nitrokey-test crate.

Adjust OTP tests to use nitrokey-test

2019-01-05T09:28:37Z

This change adjusts the OTP tests to use the nitrokey-test crate.

Use nitrokey-test for nitrokey device tests

2019-01-05T09:26:16Z

This change is the first in a series to migrate the existing tests to using the nitrokey-test crate. The crate provides a couple of benefits over the existing way testing works: - test execution is automatically serialized (i.e., no more need for --test-threads) - available devices are detected at runtime (i.e., no more need for --features test-pro) - tests capable of running only on a specific device are automatically skipped if this device is not present In addition to that, the crate also offers selection of particular groups of tests by virtue of the NITROKEY_TEST_GROUP environment variable. If set (valid values are "nodev", "pro", and "storage") only tests of the particular group are run (those tests will fail if a required precondition is not met, i.e., if a device is present but "nodev" is set, or if the "pro" group is run but no device or a storage device is present). Unfortunately, it has some limitations as well. Most importantly Rust does not allow us to indicate whether a test has been skipped or not. While it has #[ignore] support, that strictly is a compile-time feature and, hence, not usable. This patch in particular pulls in the nitrokey-test crate and adjusts the existing device tests to make use of it.

Update documentation and test for factory_reset

2019-01-03T23:51:00Z

Contrary to my previous beliefs, build_aes_key has to be called even after a factory reset using the Nitrokey API. This patch updates the documentation and the unit tests based on this insight.

Add Device::build_aes_key method

2019-01-03T17:06:30Z

This patch adds the build_aes_key method to the Device trait that uses the NK_build_aes_key function to build new AES keys on the device. This effectively resets the password safe and the encrypted storage. It is unclear whether other data (e. g. the one-time passwords) are affected too.

Add Device::factory_reset method

2019-01-03T13:53:06Z

This patch adds the factory_reset_method to the Device trait that uses the NK_factory_reset function to perform a factory reset. The tests verify that the user and admin PIN are reset and that the OTP storage and the password safe are deleted.