cert_verify_proc_android.cc should not hard-code authentication type |
||||
Issue descriptionhttps://cs.chromium.org/chromium/src/net/cert/cert_verify_proc_android.cc?rcl=0&l=36 I don't think it matters because Android seems to ignore it altogether, but we should route the type through. In theory Android could decide to check key usage from it.
,
Jul 11 2016
Ah. In that case we should have a comment that Android officially recommends not to bother with that field rather than a TODO.
,
Jul 6 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/6e3a683655be19279d1059ea1c9a62568a270226 commit 6e3a683655be19279d1059ea1c9a62568a270226 Author: David Benjamin <davidben@chromium.org> Date: Thu Jul 06 14:59:09 2017 Remove TODO. See comment #1 on associated bug. Bug: 627154 Change-Id: Ic32630ddda478593d1b6f5524579e65a47561eaf Reviewed-on: https://chromium-review.googlesource.com/560149 Commit-Queue: Ryan Sleevi <rsleevi@chromium.org> Reviewed-by: Ryan Sleevi <rsleevi@chromium.org> Cr-Commit-Position: refs/heads/master@{#484593} [modify] https://crrev.com/6e3a683655be19279d1059ea1c9a62568a270226/net/cert/cert_verify_proc_android.cc
,
Jul 6 2017
,
Jul 6 2017
,
Dec 13
Issue 162720 has been merged into this issue. |
||||
►
Sign in to add a comment |
||||
Comment 1 by rsleevi@chromium.org
, Jul 11 2016