Lines Matching +full:technical +full:- +full:documentation

5 -----
21 -------
29 Linux kernel security team (:ref:`Documentation/admin-guide/
32 The team can be contacted by email at <hardware-security@kernel.org>. This
50   - Linus Torvalds (Linux Foundation Fellow)
51   - Greg Kroah-Hartman (Linux Foundation Fellow)
52   - Thomas Gleixner (Linux Foundation Fellow)
54 Operation of mailing-lists
57 The encrypted mailing-lists which are used in our process are hosted on
69 Non-disclosure agreements
70 -------------------------
73 unable to enter into any non-disclosure agreements.  The kernel community
79 ---------------------------
96 the issue in the best technical way.
101 mailing-lists. In addition, the hardware security team will also exclude
113 face-to-face meetings are almost impossible to address hardware security
128 The hardware security team will provide an incident-specific encrypted
129 mailing-list which will be used for initial discussion with the reporter,
141 While individual developers might be covered by a non-disclosure agreement
142 via their employer, they cannot enter individual non-disclosure agreements
150  - The list of disclosed entities allows communication accross the
153  - The disclosed entities can be contacted to name experts who should
156  - If an expert which is required to handle an issue is employed by an
165 team via the specific encrypted mailing-list.
167 From our experience the technical documentation of these issues is usually
168 a sufficient starting point and further technical clarification is best
174 The initial response team sets up an encrypted mailing-list or repurposes
177 Using a mailing-list is close to the normal Linux development process and
181 The mailing-list operates in the same way as normal Linux development.
183 non-public git repository which is only accessible to the participating
219 dates or other non-technical reasons is creating more work and burden for
229 provided by the disclosing party they can be used for documentation
233 -------------------
267 Encrypted mailing-lists
268 -----------------------
270 We use encrypted mailing-lists for communication. The operating principle
272 list's PGP key or with the list's S/MIME certificate. The mailing-list
273 software decrypts the email and re-encrypts it individually for each
275 about the mailing-list software and the setup which is used to ensure the
282 For initial contact see :ref:`Contact`. For incident specific mailing-lists
301 email from the mailing-list which is signed either with the list's PGP key