tree 33cb0c030c3326ccfaf665f9e424f630fcccc6a3
parent a06a1c3fec3d971599922ca9c048cee514921554
author Gilad Arnold <garnold@chromium.org> 1367652298 -0700
committer ChromeBot <chrome-bot@google.com> 1367910195 -0700

paycheck: use base64 encoding for SHA256 hashes throughout

Turns out we were using base64 when adding SHA256 data to a payload
report, but intermittently using hex encoding in error messages. This is
now fixed.

BUG=None
TEST=No mention of hex encoding in the code
TEST=gpylinted correctly
TEST=Passes unit tests

Change-Id: Id2dc2fcd154d4647cc1a076579dde7a789c09e40
Reviewed-on: https://gerrit.chromium.org/gerrit/50104
Reviewed-by: Gilad Arnold <garnold@chromium.org>
Tested-by: Gilad Arnold <garnold@chromium.org>
Commit-Queue: David James <davidjames@chromium.org>