Google Git
Sign in
chromium / chromium / src.git / bb0b03e29b8951d3092a76ef6d87e5cc194562f0
commitbb0b03e29b8951d3092a76ef6d87e5cc194562f0[log] [tgz]
authorMatthew Denton <[email protected]>Thu Jul 22 16:18:13 2021
committerChromium LUCI CQ <[email protected]>Thu Jul 22 16:18:13 2021
tree35d8c9ba52de9f8b9ce58c58a6fe0a3a97243437
parent7c1f3c31208a278f50c8b274853a2a723cb4ef68 [diff]
Linux: Add ability to reset stack canaries after fork

Stack protectors remain the same after forking, so reading the stack
protector in one process (e.g. a renderer) reveals to an attacker the
stack protector of the ancestor zygote and its children, including
future children.

This CL adds the capability to reset stack canaries after fork, which
requires the functions already on the call stack to be compiled without
stack protectors (or else they will use the original canary and crash
on return).

A command line flag is added to enable the behavior, which will be added
by default to the chrome command line in a future CL.

Bug: 1206626
Change-Id: I26e53c91986eda2bdf238bf912832649b7a14327
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2895917
Reviewed-by: Nico Weber <[email protected]>
Reviewed-by: Avi Drissman <[email protected]>
Reviewed-by: Robert Sesek <[email protected]>
Commit-Queue: Matthew Denton <[email protected]>
Cr-Commit-Position: refs/heads/master@{#904353}
10 files changed
tree: 35d8c9ba52de9f8b9ce58c58a6fe0a3a97243437
  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. .vpython
  62. .vpython3
  63. .yapfignore
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. DEPS
  69. DIR_METADATA
  70. ENG_REVIEW_OWNERS
  71. LICENSE
  72. LICENSE.chromium_os
  73. OWNERS
  74. PRESUBMIT.py
  75. PRESUBMIT_test.py
  76. PRESUBMIT_test_mocks.py
  77. README.md
  78. 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.