Google Git
Sign in
chromium / chromiumos / docs / e44fe37f441d1c2cc876bfe789323c48b729858d
commite44fe37f441d1c2cc876bfe789323c48b729858d[log] [tgz]
authorJorge Lucangeli Obes <jorgelo@google.com>Wed Feb 06 19:06:46 2019
committerchrome-bot <chrome-bot@chromium.org>Thu Feb 07 20:38:23 2019
tree494af983ee1185a7757f5946bc07c9605f81edf1
parentff3f4e1b272a1f5b47d74140b64661cd2915dc28 [diff]
reporting_bugs: Add note about physically-local attackers.

It was pointed out that we were not properly explaining that certain
physically-local attacks are indeed in Chrome OS' threat model. Fix
that.

BUG=None
TEST=Open in Markdown viewer.

Change-Id: I4dbc4d0af393d41ff31355e693ae2614dec40f28
Reviewed-on: https://chromium-review.googlesource.com/1456383
Commit-Ready: Jorge Lucangeli Obes <jorgelo@chromium.org>
Tested-by: Jorge Lucangeli Obes <jorgelo@chromium.org>
Reviewed-by: Dan Erat <derat@chromium.org>
1 file changed
tree: 494af983ee1185a7757f5946bc07c9605f81edf1
  1. images/
  2. scripts/
  3. archive_mirrors.md
  4. ca_certs.md
  5. chrome_commit_pipeline.md
  6. COMMIT-QUEUE.ini
  7. contact.md
  8. containers_and_vms.md
  9. contributing.md
  10. cros_commit_pipeline.md
  11. cros_vm.md
  12. dbus_best_practices.md
  13. dbus_in_chrome.md
  14. debug_buttons.md
  15. developer_guide.md
  16. development_basics.md
  17. eol_aue_process.md
  18. fuzzing.md
  19. glossary.md
  20. gsutil.md
  21. kernel_faq.md
  22. lsb-release.md
  23. navbar.md
  24. os_config.md
  25. platform2_gn.md
  26. PRESUBMIT.cfg
  27. README.md
  28. reporting_bugs.md
  29. rust_on_cros.md
  30. sandboxing.md
  31. security_review_howto.md
  32. security_severity_guidelines.md
  33. security_sheriffing.md
  34. simple_chrome_workflow.md
  35. source_layout.md
  36. 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.

See the Contributing guide for more details.

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 scripts/preview_docs:

scripts/preview_docs README.md

You can also use md_browser, which is entirely local and does not require refs/sandbox/ push permission, but has somewhat inaccurate rendering:

# 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.