aboutsummaryrefslogtreecommitdiff
path: root/crypto/hash.c
diff options
context:
space:
mode:
authorDaniel P. Berrange <berrange@redhat.com>2016-09-07 12:43:29 +0100
committerDaniel P. Berrange <berrange@redhat.com>2016-09-19 16:30:45 +0100
commite74aabcffb74e6c15de05255480d43771ec63d8b (patch)
treeafe834d8b8f613b933bcc20e2c2f88e712d58564 /crypto/hash.c
parent8813800b7d995d8b54ef0a1e16d41fc13d8b5f3a (diff)
downloadqemu-e74aabcffb74e6c15de05255480d43771ec63d8b.zip
qemu-e74aabcffb74e6c15de05255480d43771ec63d8b.tar.gz
qemu-e74aabcffb74e6c15de05255480d43771ec63d8b.tar.bz2
crypto: use correct derived key size when timing pbkdf
Currently when timing the pbkdf algorithm a fixed key size of 32 bytes is used. This results in inaccurate timings for certain hashes depending on their digest size. For example when using sha1 with aes-256, this causes us to measure time for the master key digest doing 2 sha1 operations per iteration, instead of 1. Instead we should pass in the desired key size to the timing routine that matches the key size that will be used for real later. Reviewed-by: Eric Blake <eblake@redhat.com> Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Diffstat (limited to 'crypto/hash.c')
0 files changed, 0 insertions, 0 deletions