platform2: Update libchrome to r381699
Made necessary code fixes for changed APIs, include header dependencies,
etc.
The non-trivial change is around the fact that the signature of
crypto::SignatureVerifier::VerifyInit has changed and now it takes
a crypto algorithm enum value instead of AlgorithmID in ASN.1 format.
login_manager used only SHA1-with-RSA-Encryption algorithm, so I have
removed the explict algorithm ID throughout NSSUtil class and only at
the place where Chrome's crypto call was made, I switched to use the enum
value of crypto::SignatureVerifier::RSA_PKCS1_SHA1 which is the same algorithm.
Verified this by making sure all the login_manager's unit tests still pass.
BUG=None
TEST=./build_packages --board={link|whirlwind}
cbuildbot -g "333972 334011 *251854 *251867" --remote whirlwind-paladin link-paladin veyron_minnie-cheets-paladin mixed-a-pre-cq
FEATURES=test emerge-link chromeos-login
CQ-DEPEND=CL:334011
Change-Id: I78d621fba7b65970358a86e05ea97d89679ba5f8
Reviewed-on: https://chromium-review.googlesource.com/333972
Commit-Ready: Alex Vakulenko <avakulenko@google.com>
Tested-by: Alex Vakulenko <avakulenko@google.com>
Reviewed-by: Christopher Wiley <wiley@chromium.org>
Reviewed-by: Alex Deymo <deymo@chromium.org>
12 files changed
