diff options
author | Nick Mathewson <nickm@torproject.org> | 2013-08-01 12:13:09 -0400 |
---|---|---|
committer | Nick Mathewson <nickm@torproject.org> | 2013-08-15 12:03:37 -0400 |
commit | fd6749203ed9ca27263e895b53a12a6d15878cdd (patch) | |
tree | 3330a593c906e8d567006cafbd0a7b3fc849a35d /src/common/crypto.c | |
parent | 4526c3e0b617bd179bb0728ac2ea438e9a2276ed (diff) | |
download | tor-fd6749203ed9ca27263e895b53a12a6d15878cdd.tar.gz tor-fd6749203ed9ca27263e895b53a12a6d15878cdd.zip |
More unit tests for handle_client_auth_nonce
Incidentally, this business here where I make crypto_rand mockable:
this is exactly the kind of thing that would make me never want to
include test-support stuff in production builds.
Diffstat (limited to 'src/common/crypto.c')
-rw-r--r-- | src/common/crypto.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/common/crypto.c b/src/common/crypto.c index 730ce08286..6f1a0bca57 100644 --- a/src/common/crypto.c +++ b/src/common/crypto.c @@ -2404,8 +2404,8 @@ crypto_seed_rng(int startup) /** Write <b>n</b> bytes of strong random data to <b>to</b>. Return 0 on * success, -1 on failure. */ -int -crypto_rand(char *to, size_t n) +MOCK_IMPL(int, +crypto_rand, (char *to, size_t n)) { int r; tor_assert(n < INT_MAX); |