docs: Update Security Severity Guidelines

This updates the security severity guidelines to clarify that an exploit
chain is a typical form of critical vulnerability, but not necessarily a
common bug.

BUG=chromium:823893
TEST=none

Change-Id: Ia278364f959eb0b382ec8ba3ae6089b1acc65a17
Reviewed-on: https://chromium-review.googlesource.com/990479
Commit-Ready: Greg Kerr <kerrnel@chromium.org>
Tested-by: Greg Kerr <kerrnel@chromium.org>
Reviewed-by: Eric Lawrence <elawrence@chromium.org>
Reviewed-by: Jorge Lucangeli Obes <jorgelo@chromium.org>
1 file changed
tree: 70c6380a560aac96c553158764f9d43dfcc20fd1
  1. chrome_commit_pipeline.md
  2. COMMIT-QUEUE.ini
  3. cros_commit_pipeline.md
  4. cros_vm.md
  5. dbus_best_practices.md
  6. dbus_in_chrome.md
  7. development_basics.md
  8. README.md
  9. reporting_bugs.md
  10. rust_on_cros.md
  11. sandboxing.md
  12. security_severity_guidelines.md
  13. simple_chrome_workflow.md
  14. unit_tests.md
README.md

Chromium OS docs

This directory contains public Chromium OS project documentation that is automatically rendered by Gitiles. The docs are written in Gitiles-flavored Markdown.

General guidelines

See the Chromium documentation guidelines and Chromium documentation best practices.

Style guide

Markdown documents must follow the style guide.

Making changes

This repository is managed by the repo tool, so you can make changes to it using the same techniques that you'd use for any other repositories in the project. Feel free to bypass the commit queue and commit changes immediately after they are reviewed.

Making changes without repo

You can also make changes to this repository without using the repo tool. This comes in handy when you don't have a Chromium OS checkout:

git clone https://chromium.googlesource.com/chromiumos/docs
curl -Lo .git/hooks/commit-msg https://gerrit-review.googlesource.com/tools/hooks/commit-msg
chmod +x .git/hooks/commit-msg
cd docs
git checkout -b changes
(make some changes)
git commit -a
git push origin HEAD:refs/for/master

The above steps will upload a patch to chromium-review.googlesource.com where you can get your patch reviewed, and submit.

Previewing changes

You can preview your local changes using md_browser:

# at top of Chromium OS checkout
./chromium/src/tools/md_browser/md_browser.py -d docs

Then browse to e.g. http://localhost:8080/README.md.

To review someone else's changes, apply them locally first, or just click the gitiles link near the top of a Gerrit file diff page.