Update nitrokey crate to 0.4.0

This change finally updates the version of the nitrokey crate that we
consume to 0.4.0. Along with that we update rand_core, one of its
dependencies, to 0.5.1. Further more we add cfg-if in version 0.1.10 and
getrandom in version 0.1.13, both of which are now new (non-development)
dependencies.

Import subrepo nitrokey/:nitrokey at e81057037e9b4f370b64c0a030a725bc6bdfb870
Import subrepo cfg-if/:cfg-if at 4484a6faf816ff8058088ad857b0c6bb2f4b02b2
Import subrepo getrandom/:getrandom at d661aa7e1b8cc80b47dabe3d2135b3b47d2858af
Import subrepo rand/:rand at d877ed528248b52d947e0484364a4e1ae59ca502

1 files changed, 28 insertions, 0 deletions

diff --git a/rand/rand_jitter/tests/mod.rs b/rand/rand_jitter/tests/mod.rs
new file mode 100644
index 0000000..961dc27
--- /dev/null
+++ b/rand/rand_jitter/tests/mod.rs
@@ -0,0 +1,28 @@
+use rand_jitter::JitterRng;
+#[cfg(feature = "std")]
+use rand_core::RngCore;
+
+#[cfg(feature = "std")]
+#[test]
+fn test_jitter_init() {
+    // Because this is a debug build, measurements here are not representive
+    // of the final release build.
+    // Don't fail this test if initializing `JitterRng` fails because of a
+    // bad timer (the timer from the standard library may not have enough
+    // accuracy on all platforms).
+    match JitterRng::new() {
+        Ok(ref mut rng) => {
+            // false positives are possible, but extremely unlikely
+            assert!(rng.next_u32() | rng.next_u32() != 0);
+        },
+        Err(_) => {},
+    }
+}
+
+#[test]
+fn test_jitter_bad_timer() {
+    fn bad_timer() -> u64 { 0 }
+    let mut rng = JitterRng::new_with_timer(bad_timer);
+    assert!(rng.test_timer().is_err());
+}
+