[Nearby] Do not log error for key decryption failure
Even if a metadata encryption key is decrypted successfully, i.e., bytes are returned, it might not correspond to the intended key. This is expected for Nearby Share because we try to decrypt the metadata encryption keys for all public certificates until we find the right one. Key decryption failures and mismatched key commitments will be common, so do not log errors. Change-Id: Ia916db644dc5e33bb7647a6cd0b3f925b22d3630 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2350301 Commit-Queue: Josh Nohle <nohle@chromium.org> Commit-Queue: James Vecore <vecore@google.com> Auto-Submit: Josh Nohle <nohle@chromium.org> Reviewed-by:James Vecore <vecore@google.com> Cr-Commit-Position: refs/heads/master@{#797031}
Showing
Please register or sign in to comment