aboutsummaryrefslogtreecommitdiff
path: root/src/common/crypto.c
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2004-06-01 16:36:56 +0000
committerRoger Dingledine <arma@torproject.org>2004-06-01 16:36:56 +0000
commit8ca162c472e97c53a8c57ce46c2144b4628bed04 (patch)
treea5dbe4515ce0464cefcafd4ff45b0704d4ac6ecd /src/common/crypto.c
parent834ffa358fc0bc61cfb22b647c437ad1bc58269f (diff)
downloadtor-8ca162c472e97c53a8c57ce46c2144b4628bed04.tar
tor-8ca162c472e97c53a8c57ce46c2144b4628bed04.tar.gz
put a comment reminding us that we do hashes in software only
svn:r1925
Diffstat (limited to 'src/common/crypto.c')
-rw-r--r--src/common/crypto.c5
1 files changed, 5 insertions, 0 deletions
diff --git a/src/common/crypto.c b/src/common/crypto.c
index 1c265628a..17e71487a 100644
--- a/src/common/crypto.c
+++ b/src/common/crypto.c
@@ -1018,6 +1018,11 @@ crypto_digest_add_bytes(crypto_digest_env_t *digest, const char *data,
{
tor_assert(digest);
tor_assert(data);
+ /* Using the SHA1_*() calls directly means we don't support doing
+ * sha1 in hardware. But so far the delay of getting the question
+ * to the hardware, and hearing the answer, is likely higher than
+ * just doing it ourselves. Hashes are fast.
+ */
SHA1_Update(&digest->d, (void*)data, len);
}