Lines Matching refs:security

7 1. Allow LLVM contributors and security researchers to disclose security-related issues affecting t…
11 5. Ensure timely notification to users of LLVM-based toolchains whose compiled code is security-sen…
12 6. Strive to improve security over time, for example by adding additional testing, fuzzing, and har…
18 .. _report-security-issue:
20 How to report a security issue?
23 To report a security issue in the LLVM Project, please `open a new issue`_ in the LLVM project page…
63 …+ Specializes in fixing compiler-based security related issues or often participates in their expl…
64 …+ Has a track record of finding security vulnerabilities and responsible disclosure of those vulne…
65 …has specific interests in knowing about, resolving, and preventing future security vulnerabilities.
70 …+ Has a track record of finding security vulnerabilities and responsible disclosure of those vulne…
71 …has specific interests in knowing about, resolving, and preventing future security vulnerabilities.
75 …on in the organization, the nominee has a reasonable need to know about security issues and disclo…
79 …- If already in the LLVM Security Group, has actively participated in one (if any) security issue …
103 … successful nominee should accept membership and agree to abide by this security policy, particula…
128 …f security issues, as well as process discussions about matters such as disclosure timelines and g…
133 Members of the LLVM Security Group will be expected to treat LLVM security issue information shared…
135 * Members should not disclose security issue information to non-members unless both members are emp…
152 * Help write and review patches to address security issues.
160 It seems like bugzilla and email don't meet security requirements.
162 …M Security Group discussions is security-sensitive. It should therefore run on infrastructure whic…
164 We are currently using the `chromium issue tracker`_ (as the `llvm` project) to have security discu…
166 * File security issues.
167 * Discuss security improvements to LLVM.
171 …security`_ workflow allows publicly disclosing resolved security issues on the github project page…
187 * A security issue reporter (not necessarily an LLVM contributor) reports an issue.
189 …n which circumstances (if any) an issue is relevant to security, and determine if it is a security…
193 * Backporting security patches from recent versions to old versions cannot always work. It is up to…
198 * All security issues (as well as nomination / removal discussions) become public within approximat…
207 What is considered a security issue?
210 …l be expanded once the Security Group is formed, and it agrees on an initial security surface area.
212 …security-sensitive. This is particularly true because LLVM is used in a wide variety of circumstan…
214 …security process matures, members of the LLVM community can propose that a part of the codebase be…
216 If you're not sure whether an issue is in-scope for this security process or not, err towards assum…
218 The security-sensitive parts of the LLVM Project currently are:
223 The parts of the LLVM Project which are currently treated as non-security sensitive are:
232 .. _GitHub security: https://help.github.com/en/articles/about-maintainer-security-advisories