Lines Matching +full:vendor +full:- +full:specific
7 -----
23 -------
31 Linux kernel security team (:ref:`Documentation/admin-guide/
34 The team can be contacted by email at <hardware-[email protected]>. This
43 - PGP: https://www.kernel.org/static/files/hardware-security.asc
44 - S/MIME: https://www.kernel.org/static/files/hardware-security.crt
47 vendor, we welcome contact from researchers or individuals who have
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 ---------------------------
118 face-to-face meetings are almost impossible to address hardware security
135 The hardware security team will provide an incident-specific encrypted
148 While individual developers might be covered by a non-disclosure agreement
149 via their employer, they cannot enter individual non-disclosure agreements
157 - The list of disclosed entities allows communication across the
160 - The disclosed entities can be contacted to name experts who should
163 - If an expert who is required to handle an issue is employed by a listed
172 team via the specific encrypted mailing-list.
181 The initial response team sets up an encrypted mailing-list or repurposes
190 a non-public git repository which is only accessible to the participating
235 vendor’s response team. The representative must notify the kernel
236 response team about the handover. The affected silicon vendor must
241 The silicon vendor’s response team can distribute these patches to
243 silicon vendor’s documented security process. Feedback from the
244 industry partners goes back to the silicon vendor and is
245 communicated by the silicon vendor to the kernel response team.
247 The handover to the silicon vendor’s response team removes any
250 silicon vendor’s internal teams or industry partners. The silicon
251 vendor guarantees this release of liability by agreeing to this
259 relevant kernel trees. There is no pre-notification process: the
267 dates or other non-technical reasons creates more work and burden for the
281 -------------------
297 RISC-V Palmer Dabbelt <[email protected]>
316 understand and support our process fully and is ideally well-connected in
319 Encrypted mailing-lists
320 -----------------------
325 software decrypts the email and re-encrypts it individually for each
335 specific mailing lists, the key and S/MIME certificate are conveyed to the
336 subscribers by email sent from the specific list.
338 Subscription to incident-specific lists
341 Subscription to incident-specific lists is handled by the response teams.
354 email from the mailing-list which is signed either with the list's PGP key