Rust interface to libnitrokey https://git.ireas.org/nitrokey-rs/atom?h=authentication-error 2019-07-20T08:24:51Z 2019-07-20T08:24:51Z Robin Krahl robin.krahl@ireas.org 2019-02-05T14:47:14Z urn:sha1:3a0ed1b3b81b29530c0dd5d65a5409c349f85aae 2019-07-20T08:20:07Z Robin Krahl robin.krahl@ireas.org 2019-02-05T13:05:59Z urn:sha1:e31f1bca97fd8ee36bd933fa54c53980fc5084a7 2019-07-16T09:15:35Z Robin Krahl robin.krahl@ireas.org 2019-07-16T09:14:36Z urn:sha1:678f0b700666a4ba86db2180078d79a730dc82e0 This patch splits the rather large device module into the submodules pro, storage and wrapper. This only changes the internal code structure and does not affect the public API. 2019-07-16T09:00:20Z Robin Krahl robin.krahl@ireas.org 2019-07-16T08:58:37Z urn:sha1:6c138eaa850c745b97b7e48a201db0cbaad8e1e0 This patch updates the rand_core dependency to version 0.5 and the rand_os dependency to version 0.2. This causes a change in util.rs: Instead of constructing an OsRng instance using OsRng::new(), we can directly instantiate the (now empty) struct. 2019-07-09T10:47:26Z Robin Krahl robin.krahl@ireas.org 2019-07-09T10:44:45Z urn:sha1:5e8f0fbaf6df0cb919e4b02401cc21d5280bf09c The take and take_blocking functions return a PoisonError if the cache is poisoned, i. e. if a thread panicked while holding the manager. This is a sensible default behaviour, but for example during testing, one might want to ignore the poisoned cache. This patch adds the force_take function that unwraps the PoisonError and returns the cached Manager even if the cache was poisoned. 2019-07-09T10:23:14Z Robin Krahl robin.krahl@ireas.org 2019-07-09T10:22:08Z urn:sha1:88b32f5c2187e59fece93cd245aeadb4e5f9e04a During the connection manager refactoring, we temporarily used deprecated methods. This is no longer the case, so we can remove the allow(deprecated) attribute. 2019-07-09T08:44:08Z Robin Krahl robin.krahl@ireas.org 2019-01-27T19:52:53Z urn:sha1:62e8ee8f5d02511d6eb5dc179b087b04e88c1b94 This patch updates the documentation to reflect the latest changes to connection handling. It also updates the doc tests to prefer the new methods over the old ones. 2019-07-09T08:27:55Z Robin Krahl robin.krahl@ireas.org 2019-07-09T08:09:02Z urn:sha1:12fa62483cf45d868099d5d4020333af492eebde To enable applications like nitrokey-test to go back to a manager instance from a Device instance, we add the into_manager function to the Device trait. To do that, we have to keep track of the Manager’s lifetime by adding a lifetime to Device (and then to some other traits that use Device). 2019-07-08T21:40:17Z Robin Krahl robin.krahl@ireas.org 2019-01-27T18:42:14Z urn:sha1:fe2f39826ade5a156945dabb8c8ab725378a15c1 In the last patches, we ensured that devices can only be obtained using the Manager struct. But we did not ensure that there is only one device at a time. This patch adds a mutable reference to the Manager instance to the Device implementations. The borrow checker makes sure that there is only one mutable reference at a time. In this patch, we have to remove the old connect, Pro::connect and Storage::connect functions as they do no longer compile. (They discard the MutexGuard which invalidates the reference to the Manager.) Therefore the tests do no longer compile. 2019-07-08T21:33:13Z Robin Krahl robin.krahl@ireas.org 2019-01-27T18:21:08Z urn:sha1:379bc798477a1de7ffda923c5d10ca63aebae25f As part of the connection refactoring, this patch moves the connect methods of the Pro and Storage structs into the Manager struct. To maintain compatibility with nitrokey-test, the old methods are not removed but marked as deprecated.