[go: up one dir, main page]
Google Git
Sign in
chromium / chromium / src / f668bbbbaa430bf341a3ee6a72820457cfaf2051
commitf668bbbbaa430bf341a3ee6a72820457cfaf2051[log] [tgz]
authorMatt Mueller <mattm@chromium.org>Mon Dec 13 22:06:54 2021
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Dec 13 22:06:54 2021
treecbab7bdb6bc38ed24558850d0a18e26282af9a3f
parent4ea822925bbc6a6e508820e236a6a46efee78040 [diff]
cert viewer: remove "verified usages" section

This was using the NSS certificate verifier to check whether the
certificate could be verified for various usages. This could be
misleading since we do not use the NSS verifier anymore, and further it
does not consider the actual chain and other context the certificate
was verified with.

Just remove it rather than converting to use our verifier, as it does
not add any real value anyway. At best it is redundant with the
information from the security state / page info from loading the page,
at worst it could actually have conflicting results if the exact same
input state isn't used.

(cherry picked from commit 2e12de37f1f7451b4568c68c58bb07c26ca61368)

Bug: 953425, 1278589
Change-Id: I719e266e9004c7d144370ce09b5ef6b67811ff88
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3291617
Reviewed-by: David Benjamin <davidben@chromium.org>
Reviewed-by: John Lee <johntlee@chromium.org>
Commit-Queue: Matt Mueller <mattm@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#943266}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3335190
Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Cr-Commit-Position: refs/branch-heads/4664@{#1295}
Cr-Branched-From: 24dc4ee75e01a29d390d43c9c264372a169273a7-refs/heads/main@{#929512}
10 files changed
tree: cbab7bdb6bc38ed24558850d0a18e26282af9a3f
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. cloud_print/
  13. codelabs/
  14. components/
  15. content/
  16. courgette/
  17. crypto/
  18. dbus/
  19. device/
  20. docs/
  21. extensions/
  22. fuchsia/
  23. gin/
  24. google_apis/
  25. google_update/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. jingle/
  32. media/
  33. mojo/
  34. native_client_sdk/
  35. net/
  36. pdf/
  37. ppapi/
  38. printing/
  39. remoting/
  40. rlz/
  41. sandbox/
  42. services/
  43. skia/
  44. sql/
  45. storage/
  46. styleguide/
  47. testing/
  48. third_party/
  49. tools/
  50. ui/
  51. url/
  52. weblayer/
  53. .clang-format
  54. .clang-tidy
  55. .eslintrc.js
  56. .git-blame-ignore-revs
  57. .gitattributes
  58. .gitignore
  59. .gn
  60. .mailmap
  61. .rustfmt.toml
  62. .vpython
  63. .vpython3
  64. .yapfignore
  65. AUTHORS
  66. BUILD.gn
  67. CODE_OF_CONDUCT.md
  68. codereview.settings
  69. DEPS
  70. DIR_METADATA
  71. ENG_REVIEW_OWNERS
  72. LICENSE
  73. LICENSE.chromium_os
  74. OWNERS
  75. PRESUBMIT.py
  76. PRESUBMIT_test.py
  77. PRESUBMIT_test_mocks.py
  78. README.md
  79. WATCHLISTS
README.md

Logo Chromium

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.