diff options
| author | Jan Engelhardt <jengelh@inai.de> | 2023-10-05 13:32:52 +0200 |
|---|---|---|
| committer | Siddhesh Poyarekar <siddhesh@gotplt.org> | 2023-10-05 12:00:39 -0400 |
| commit | 604e76ed867ebde255ccfac835c6f8d6fb5fd4a9 (patch) | |
| tree | b2a66606108b6d0907296bc0821583f3f62eb89a | |
| parent | 2e087957d911150258f199050bb602a6b098848c (diff) | |
| download | gcc-604e76ed867ebde255ccfac835c6f8d6fb5fd4a9.zip gcc-604e76ed867ebde255ccfac835c6f8d6fb5fd4a9.tar.gz gcc-604e76ed867ebde255ccfac835c6f8d6fb5fd4a9.tar.bz2 | |
secpol: consistent indentation
86% of the document have 4 spaces; adjust the remaining 14%.
Signed-off-by: Jan Engelhardt <jengelh@inai.de>
ChangeLog:
* SECURITY.txt: Fix up indentation.
| -rw-r--r-- | SECURITY.txt | 32 |
1 files changed, 16 insertions, 16 deletions
diff --git a/SECURITY.txt b/SECURITY.txt index 9379292..b3e2bbf 100644 --- a/SECURITY.txt +++ b/SECURITY.txt @@ -173,33 +173,33 @@ Security features implemented in GCC Reporting private security bugs =============================== - *All bugs reported in the GCC Bugzilla are public.* + *All bugs reported in the GCC Bugzilla are public.* - In order to report a private security bug that is not immediately - public, please contact one of the downstream distributions with - security teams. The following teams have volunteered to handle - such bugs: + In order to report a private security bug that is not immediately + public, please contact one of the downstream distributions with + security teams. The following teams have volunteered to handle + such bugs: Debian: security@debian.org Red Hat: secalert@redhat.com SUSE: security@suse.de AdaCore: product-security@adacore.com - Please report the bug to just one of these teams. It will be shared - with other teams as necessary. + Please report the bug to just one of these teams. It will be shared + with other teams as necessary. - The team contacted will take care of details such as vulnerability - rating and CVE assignment (http://cve.mitre.org/about/). It is likely - that the team will ask to file a public bug because the issue is - sufficiently minor and does not warrant an embargo. An embargo is not - a requirement for being credited with the discovery of a security - vulnerability. + The team contacted will take care of details such as vulnerability + rating and CVE assignment (http://cve.mitre.org/about/). It is likely + that the team will ask to file a public bug because the issue is + sufficiently minor and does not warrant an embargo. An embargo is not + a requirement for being credited with the discovery of a security + vulnerability. Reporting public security bugs ============================== - It is expected that critical security bugs will be rare, and that most - security bugs can be reported in GCC, thus making - them public immediately. The system can be found here: + It is expected that critical security bugs will be rare, and that most + security bugs can be reported in GCC, thus making + them public immediately. The system can be found here: https://gcc.gnu.org/bugzilla/ |