Google Git
Sign in
chromium / chromium / src / 8feab125f1d17b8d815f7cfc0a82e906de51d409
commit8feab125f1d17b8d815f7cfc0a82e906de51d409[log] [tgz]
authorRyan Dickson <ryandickson@google.com>Tue Jan 28 20:47:13 2025
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Jan 28 20:47:13 2025
tree8c793477f7040d5b4d4d40c783ee6a66f72d65de
parent48b77f350de18c52e7a6d242c7ac34aa3ef55708 [diff]
Chrome Root Store FAQ update - January 2025

This CL adds two FAQ items, described below.

1. “What does it mean for a certificate in the Chrome Root Store to be constrained?” This is important now that we have entries within the root store that are constrained - and due to recent updates to the presentation of the root store contents via root_store.md.

2. “What happens when a certificate is added to or removed from the Chrome Root Store?” This is intended to more clearly describe how updated versions of the Chrome Root Store impact Chrome users.

Change-Id: I092e568e6621bc8fd25363c12623cb61632d58db
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6195058
Reviewed-by: Hubert Chao <hchao@chromium.org>
Reviewed-by: Matt Mueller <mattm@chromium.org>
Commit-Queue: Ryan Dickson <ryandickson@google.com>
Cr-Commit-Position: refs/heads/main@{#1412509}
1 file changed
tree: 8c793477f7040d5b4d4d40c783ee6a66f72d65de
  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. codelabs/
  13. components/
  14. content/
  15. crypto/
  16. dbus/
  17. device/
  18. docs/
  19. extensions/
  20. fuchsia_web/
  21. gin/
  22. google_apis/
  23. gpu/
  24. headless/
  25. infra/
  26. ios/
  27. ipc/
  28. media/
  29. mojo/
  30. native_client_sdk/
  31. net/
  32. pdf/
  33. ppapi/
  34. printing/
  35. remoting/
  36. rlz/
  37. sandbox/
  38. services/
  39. skia/
  40. sql/
  41. storage/
  42. styleguide/
  43. testing/
  44. third_party/
  45. tools/
  46. ui/
  47. url/
  48. webkit/
  49. clank
  50. internal
  51. ios_internal
  52. native_client
  53. signing_keys
  54. v8
  55. .clang-format
  56. .clang-tidy
  57. .clangd
  58. .git-blame-ignore-revs
  59. .gitallowed
  60. .gitattributes
  61. .gitignore
  62. .gitmodules
  63. .gn
  64. .mailmap
  65. .rustfmt.toml
  66. .vpython3
  67. .yapfignore
  68. ATL_OWNERS
  69. AUTHORS
  70. BUILD.gn
  71. CODE_OF_CONDUCT.md
  72. codereview.settings
  73. CPPLINT.cfg
  74. CRYPTO_OWNERS
  75. DEPS
  76. description
  77. DIR_METADATA
  78. LICENSE
  79. LICENSE.chromium_os
  80. OWNERS
  81. PRESUBMIT.py
  82. PRESUBMIT_test.py
  83. PRESUBMIT_test_mocks.py
  84. README.md
  85. 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.