Lines Matching refs:security

11 are in the scope of this security process (including experimental APIs).
22 If in doubt, please consider the vulnerability as security sensitive.
29 There is no pro-active security engineering effort at the moment.
31 Please report any security issue you find in DPDK as described below.
39 to `security@dpdk.org <https://core.dpdk.org/security#contact>`_.
43 <https://mails.dpdk.org/roster/security>`_.
46 as part of the security process.
66 Upon reception of the report, a security team member should reply
69 The DPDK security team reviews the security vulnerability reported.
70 Area experts not members of the security team may be involved in the process.
71 In case the reported issue is not qualified as a security vulnerability,
72 the security team will request the submitter to report it
74 If qualified, the security team will assess which DPDK version are affected.
76 <https://bugs.dpdk.org/buglist.cgi?f1=bug_group&o1=equals&v1=security>`_)
79 The security team calculates the severity score with
85 If an embargo is decided, its duration should be suggested by the security team
105 The security team develops a security advisory document.
106 The security team may, at its discretion,
107 include the reporter (via "CC") in developing the security advisory document,
110 When the document is final, the security team needs to
116 (see `contact details <https://access.redhat.com/security/team/contact>`_).
138   { DPDK_security_team_member }, on behalf of the DPDK security team
158   { DPDK_security_team_member }, on behalf of the DPDK security team
170 by the security team and
181 When the fix is ready, the security advisory and patches are sent
183 (`security[email protected] <mailto:security[email protected]>`_),
190 Downstream stakeholders (in `security-prerelease list
191 <https://mails.dpdk.org/roster/security-prerelease>`_), are:
197 The `OSS security private mailing list mailto:[email protected]>` will
199 OSS-security process <https://oss-security.openwall.org/wiki/mailing-lists/distros>`
205 The security advisory will be based on below template,
206 and will be sent signed with a security team's member GPG key.
242 a security advisory is sent to downstream stakeholders
243 (`security[email protected] <mailto:security[email protected]>`_),
277 * The assigned bug is filled by a member of the security team,
284 do not have to deal with security updates over the weekend.
286 The security advisory is posted
287 to `[email protected] <mailto:[email protected]>`_ and to `the public OSS-security
288 mailing list <mailto:oss-security@lists.openwall.com>` as soon as the patches
318 * `A minimal security response process