diff options
| author | Adin Scannell <ascannell@google.com> | 2019-04-05 23:21:26 -0700 |
|---|---|---|
| committer | Adin Scannell <adin@scannell.ca> | 2019-04-08 11:30:38 -0700 |
| commit | c23efc31e2721ed192b19d082553cb99a391d24e (patch) | |
| tree | dbd862056deef5c4f4f67c6ec4097ea2793acc9f /content | |
| parent | 6fd3df4df8c0c657833d56affadd852fa748995d (diff) | |
Update markdown formatting in security.md
Diffstat (limited to 'content')
| -rw-r--r-- | content/docs/architecture_guide/security.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/content/docs/architecture_guide/security.md b/content/docs/architecture_guide/security.md index 5f02962ad..fc2a7bf7a 100644 --- a/content/docs/architecture_guide/security.md +++ b/content/docs/architecture_guide/security.md @@ -192,7 +192,7 @@ Additionally, we have practical restrictions that are imposed on the project to minimize the risk of Sentry exploitability. For example: 1. Unsafe code is carefully controlled. All unsafe code is isolated in files - that end with “_unsafe.go”, in order to facilitate validation and auditing. + that end with "unsafe.go", in order to facilitate validation and auditing. No file without the unsafe suffix may import the unsafe package. 1. No CGo is allowed. The Sentry must be a pure Go binary. 1. External imports are not generally allowed within the core packages. Only |