diff options
author | iphydf <iphydf@users.noreply.github.com> | 2016-11-06 15:14:02 +0000 |
---|---|---|
committer | iphydf <iphydf@users.noreply.github.com> | 2016-11-09 22:30:49 +0000 |
commit | aed24408db9cd8afe632a1d3f056669ae34f49be (patch) | |
tree | 77cb037490b3f97af949eb39dfdf2e1e513b61d1 /toxcore/onion_client.c | |
parent | 42dfdf73c1dfd899a4f5a44ea1584aaf3a4ed3d2 (diff) |
Remove new_nonce function in favour of random_nonce.
`new_nonce` has been an alias for `random_nonce` for a while now. Having
two names for the same operation is confusing. `random_nonce` better
expresses the intent. The documentation for `new_nonce` talks about
guaranteeing that the nonce is different from previous ones, which is
incorrect, it's just quite likely to be different.
Diffstat (limited to 'toxcore/onion_client.c')
-rw-r--r-- | toxcore/onion_client.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/toxcore/onion_client.c b/toxcore/onion_client.c index 86f4de72..c03036ac 100644 --- a/toxcore/onion_client.c +++ b/toxcore/onion_client.c | |||
@@ -949,7 +949,7 @@ static int send_dht_dhtpk(const Onion_Client *onion_c, int friend_num, const uin | |||
949 | } | 949 | } |
950 | 950 | ||
951 | uint8_t nonce[crypto_box_NONCEBYTES]; | 951 | uint8_t nonce[crypto_box_NONCEBYTES]; |
952 | new_nonce(nonce); | 952 | random_nonce(nonce); |
953 | 953 | ||
954 | uint8_t temp[DATA_IN_RESPONSE_MIN_SIZE + crypto_box_NONCEBYTES + length]; | 954 | uint8_t temp[DATA_IN_RESPONSE_MIN_SIZE + crypto_box_NONCEBYTES + length]; |
955 | memcpy(temp, onion_c->c->self_public_key, crypto_box_PUBLICKEYBYTES); | 955 | memcpy(temp, onion_c->c->self_public_key, crypto_box_PUBLICKEYBYTES); |