diff options
| author | Robin Krahl <robin.krahl@ireas.org> | 2019-01-03 23:48:22 +0000 |
|---|---|---|
| committer | Robin Krahl <robin.krahl@ireas.org> | 2019-01-04 00:51:00 +0100 |
| commit | c5d5ab12ab8ca6b9889550f050b859b76fa4bdd7 (patch) | |
| tree | df703b4b54ac890b200b432207ba8d5c18322ec5 /tests | |
| parent | 7b4c1f73be9d430ebff698794a482d0a374b8dc9 (diff) | |
| download | nitrokey-rs-c5d5ab12ab8ca6b9889550f050b859b76fa4bdd7.tar.gz nitrokey-rs-c5d5ab12ab8ca6b9889550f050b859b76fa4bdd7.tar.bz2 | |
Update documentation and test for factory_reset
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.
Diffstat (limited to 'tests')
| -rw-r--r-- | tests/device.rs | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/tests/device.rs b/tests/device.rs index 06e014e..0ad4987 100644 --- a/tests/device.rs +++ b/tests/device.rs @@ -344,6 +344,8 @@ fn factory_reset() { assert_ne!("test".to_string(), pws.get_slot_name(0).unwrap()); assert_ne!("testlogin".to_string(), pws.get_slot_login(0).unwrap()); assert_ne!("testpw".to_string(), pws.get_slot_password(0).unwrap()); + + assert_eq!(Ok(()), device.build_aes_key(ADMIN_PASSWORD)); } #[test] |