hashtables: get_random_int is now more secure, so expose directly

On 4.11, get_random_u32 now either uses chacha or rdrand, rather than
the horrible former MD5 construction, so we feel more comfortable
exposing RNG output directly.

On older kernels, we fall back to something a bit disgusting.

Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

1 files changed, 0 insertions, 1 deletions

diff --git a/src/hashtables.h b/src/hashtables.h
index c66780a..9fa47d5 100644
--- a/src/hashtables.h
+++ b/src/hashtables.h
@@ -24,7 +24,6 @@ struct wireguard_peer *pubkey_hashtable_lookup(struct pubkey_hashtable *table, c
 
 struct index_hashtable {
 	DECLARE_HASHTABLE(hashtable, 10);
-	siphash_key_t key;
 	spinlock_t lock;
 };