| commit | 8813800b7d995d8b54ef0a1e16d41fc13d8b5f3a | |
| author | Daniel P. Berrange <berrange@redhat.com> | |
| Wed, 7 Sep 2016 11:38:07 +0000 (7 12:38 +0100) | ||
| committer | Daniel P. Berrange <berrange@redhat.com> | |
| Mon, 19 Sep 2016 15:30:45 +0000 (19 16:30 +0100) | ||
| tree | d04d3dae6771a415193fbf92d955075a88932d4f | treesnapshot (tar.gz zip) |
| parent | 3bd18890cab82735ae2565fa50aa122e1b4a0ef0 | commitdiff |
crypto: clear out buffer after timing pbkdf algorithm
The 'out' buffer will hold a key derived from master
password, so it is best practice to clear this buffer
when no longer required.
At this time, the code isn't worrying about locking
buffers into RAM to prevent swapping sensitive data
to disk.
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
The 'out' buffer will hold a key derived from master
password, so it is best practice to clear this buffer
when no longer required.
At this time, the code isn't worrying about locking
buffers into RAM to prevent swapping sensitive data
to disk.
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
| crypto/pbkdf.c | diffblobblamehistory |