Lines Matching +full:highly +full:- +full:integrated

7 -----
23 -------
31 Linux kernel security team (:ref:`Documentation/admin-guide/
34 The team can be contacted by email at <hardware-security@kernel.org>. This
43   - PGP: https://www.kernel.org/static/files/hardware-security.asc
44   - S/MIME: https://www.kernel.org/static/files/hardware-security.crt
55   - Linus Torvalds (Linux Foundation Fellow)
56   - Greg Kroah-Hartman (Linux Foundation Fellow)
57   - Thomas Gleixner (Linux Foundation Fellow)
59 Operation of mailing-lists
62 The encrypted mailing-lists which are used in our process are hosted on
74 Non-disclosure agreements
75 -------------------------
78 unable to enter into any non-disclosure agreements.  The kernel community
84 ---------------------------
106 mailing-lists. In addition, the hardware security team will also exclude
107 the offender from future issues. The impact of this consequence is a highly
118 face-to-face meetings are almost impossible to address hardware security
133 The hardware security team will provide an incident-specific encrypted
134 mailing-list which will be used for initial discussion with the reporter,
146 While individual developers might be covered by a non-disclosure agreement
147 via their employer, they cannot enter individual non-disclosure agreements
155  - The list of disclosed entities allows communication across the
158  - The disclosed entities can be contacted to name experts who should
161  - If an expert which is required to handle an issue is employed by an
170 team via the specific encrypted mailing-list.
179 The initial response team sets up an encrypted mailing-list or repurposes
182 Using a mailing-list is close to the normal Linux development process and
186 The mailing-list operates in the same way as normal Linux development.
188 non-public git repository which is only accessible to the participating
221 ends. At that point the prepared mitigations are integrated into the
222 relevant kernel trees and published. There is no pre-notification process:
229 dates or other non-technical reasons is creating more work and burden for
243 -------------------
259   RISC-V	Palmer Dabbelt <palmer@dabbelt.com>
281 Encrypted mailing-lists
282 -----------------------
284 We use encrypted mailing-lists for communication. The operating principle
286 list's PGP key or with the list's S/MIME certificate. The mailing-list
287 software decrypts the email and re-encrypts it individually for each
289 about the mailing-list software and the setup which is used to ensure the
296 For initial contact see :ref:`Contact`. For incident specific mailing-lists
315 email from the mailing-list which is signed either with the list's PGP key