Revert "Refactor how additional certificates are configured." This reverts commit 264e35de5242e6317773c950b3132f35544df635. Reason for revert: Builder linux-lacros-tester-rel is failing, see https://bugs.chromium.org/p/chromium/issues/detail?id=1500787 Original change's description: > Refactor how additional certificates are configured. > > Previously they were set through CertVerifier::Config and passed into > CertVerifyProc::Verify on every verification attempt. This also means > they needed to be passed from the browser to the network service on > configuration, and then passed back to the cert verifier service on > every verification attempt. > > The new flow stores them in the CertVerifyProc instance and uses the > CertVerifierWithUpdatableProc interface to update them. > > (this CL borrows some of the CertVerifierServiceUpdater parts from https://chromium-review.googlesource.com/c/chromium/src/+/4909292) > > Bug: 1477317,1427326,978854 > Change-Id: I802d1bb05e999b97bbbec2a80566ca7cf429b774 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4957815 > Reviewed-by: Dmitry Gozman <dgozman@chromium.org> > Reviewed-by: David Trainor <dtrainor@chromium.org> > Commit-Queue: Matt Mueller <mattm@chromium.org> > Reviewed-by: Matthew Denton <mpdenton@chromium.org> > Reviewed-by: Ken Buchanan <kenrb@chromium.org> > Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com> > Cr-Commit-Position: refs/heads/main@{#1221751} Bug: 1477317,1427326,978854, 1500719 Change-Id: I92e840223dea1298a4570ce7ddf1490add0d7986 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5014407 Auto-Submit: Sophia Lin <sophialin@google.com> Reviewed-by: Sophia Lin <sophialin@google.com> Owners-Override: Sophia Lin <sophialin@google.com> Commit-Queue: Sophia Lin <sophialin@google.com> Cr-Commit-Position: refs/heads/main@{#1221994}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.