Polymorphic usage of SecureBlob is problematic (see crbug.com/728047).
In some cases we're unnecessarily passing plain Blobs into functions
that take SecureBlobs because we don't have code to create a SecureBlob
from a hex string, so we use base::HexStringToBytes to create a Blob
This CL does attempt to use HexStringToBytes and then zero out the
memory. As long as we still have polymorphic usage of SecureBlobs,
this is not a big deal. Once we decouple SecureBlob from Blob, we can
improve this implementation.
TEST=New unit tests.
Commit-Ready: Jorge Lucangeli Obes <firstname.lastname@example.org>
Tested-by: Jorge Lucangeli Obes <email@example.com>
Reviewed-by: Jorge Lucangeli Obes <firstname.lastname@example.org>
3 files changed