tree 461824fa62fc565d9d4e2e5685830bd1715bea00
parent 910320a3a083a883dc9962f9368cd12efdbdc2b0
author David Benjamin <davidben@google.com> 1526400001 -0400
committer CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> 1526427692 +0000

Try both null and empty passwords when decoding PKCS#12.

PKCS#12 encodes passwords as NUL-terminated UCS-2, so the empty password
is encoded as {0, 0}. Some implementations use the empty byte array for
"no password". OpenSSL considers a non-NULL password as {0, 0} and a
NULL password as {}. It then, in high-level PKCS#12 parsing code, tries
both options.

Match this behavior to appease pyOpenSSL's tests.

Change-Id: I07ef91d54454b6f2647f86b7eb9b13509b2876d3
Reviewed-on: https://boringssl-review.googlesource.com/28550
Commit-Queue: David Benjamin <davidben@google.com>
CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
Reviewed-by: Adam Langley <agl@google.com>