Csphinx.addnodesdocument)}( rawsourcechildren]( translations LanguagesNode)}(hhh](h pending_xref)}(hhh]docutils.nodesTextChinese (Simplified)}parenthsba attributes}(ids]classes]names]dupnames]backrefs] refdomainstdreftypedoc reftarget5/translations/zh_CN/process/embargoed-hardware-issuesmodnameN classnameN refexplicitutagnamehhh ubh)}(hhh]hChinese (Traditional)}hh2sbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget5/translations/zh_TW/process/embargoed-hardware-issuesmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hItalian}hhFsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget5/translations/it_IT/process/embargoed-hardware-issuesmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hJapanese}hhZsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget5/translations/ja_JP/process/embargoed-hardware-issuesmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hKorean}hhnsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget5/translations/ko_KR/process/embargoed-hardware-issuesmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hPortuguese (Brazilian)}hhsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget5/translations/pt_BR/process/embargoed-hardware-issuesmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hSpanish}hhsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget5/translations/sp_SP/process/embargoed-hardware-issuesmodnameN classnameN refexplicituh1hhh ubeh}(h]h ]h"]h$]h&]current_languageEnglishuh1h hh _documenthsourceNlineNubhtarget)}(h.. _embargoed_hardware_issues:h]h}(h]h ]h"]h$]h&]refidembargoed-hardware-issuesuh1hhKhhhhhO/var/lib/git/docbuild/linux/Documentation/process/embargoed-hardware-issues.rstubhsection)}(hhh](htitle)}(hEmbargoed hardware issuesh]hEmbargoed hardware issues}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhhhhhKubh)}(hhh](h)}(hScopeh]hScope}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhhhhhKubh paragraph)}(hHardware issues which result in security problems are a different category of security bugs than pure software bugs which only affect the Linux kernel.h]hHardware issues which result in security problems are a different category of security bugs than pure software bugs which only affect the Linux kernel.}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK hhhhubh)}(hXHardware issues like Meltdown, Spectre, L1TF etc. must be treated differently because they usually affect all Operating Systems ("OS") and therefore need coordination across different OS vendors, distributions, silicon vendors, hardware integrators, and other parties. For some of the issues, software mitigations can depend on microcode or firmware updates, which need further coordination.h]hXHardware issues like Meltdown, Spectre, L1TF etc. must be treated differently because they usually affect all Operating Systems (“OS”) and therefore need coordination across different OS vendors, distributions, silicon vendors, hardware integrators, and other parties. For some of the issues, software mitigations can depend on microcode or firmware updates, which need further coordination.}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK hhhhubh)}(h .. _Contact:h]h}(h]h ]h"]h$]h&]hcontactuh1hhKhhhhhhubeh}(h]scopeah ]h"]scopeah$]h&]uh1hhhhhhhhKubh)}(hhh](h)}(hContacth]hContact}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhKubh)}(h`The Linux kernel hardware security team is separate from the regular Linux kernel security team.h]h`The Linux kernel hardware security team is separate from the regular Linux kernel security team.}(hj,hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubh)}(hX4The team only handles developing fixes for embargoed hardware security issues. Reports of pure software security bugs in the Linux kernel are not handled by this team and the reporter will be guided to contact the regular Linux kernel security team (:ref:`Documentation/admin-guide/ `) instead.h](hThe team only handles developing fixes for embargoed hardware security issues. Reports of pure software security bugs in the Linux kernel are not handled by this team and the reporter will be guided to contact the regular Linux kernel security team (}(hj:hhhNhNubh)}(h0:ref:`Documentation/admin-guide/ `h]hinline)}(hjDh]hDocumentation/admin-guide/}(hjHhhhNhNubah}(h]h ](xrefstdstd-refeh"]h$]h&]uh1jFhjBubah}(h]h ]h"]h$]h&]refdoc!process/embargoed-hardware-issues refdomainjSreftyperef refexplicitrefwarn reftarget securitybugsuh1hhhhKhj:ubh ) instead.}(hj:hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKhjhhubh)}(hThe team can be contacted by email at . This is a private list of security officers who will help you coordinate a fix according to our documented process.h](h'The team can be contacted by email at <}(hjqhhhNhNubh reference)}(hhardware-security@kernel.orgh]hhardware-security@kernel.org}(hj{hhhNhNubah}(h]h ]h"]h$]h&]refuri#mailto:hardware-security@kernel.orguh1jyhjqubhv>. This is a private list of security officers who will help you coordinate a fix according to our documented process.}(hjqhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhK"hjhhubh)}(hThe list is encrypted and email to the list can be sent by either PGP or S/MIME encrypted and must be signed with the reporter's PGP key or S/MIME certificate. The list's PGP key and S/MIME certificate are available from the following URLs:h]hThe list is encrypted and email to the list can be sent by either PGP or S/MIME encrypted and must be signed with the reporter’s PGP key or S/MIME certificate. The list’s PGP key and S/MIME certificate are available from the following URLs:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK&hjhhubh block_quote)}(h- PGP: https://www.kernel.org/static/files/hardware-security.asc - S/MIME: https://www.kernel.org/static/files/hardware-security.crt h]h bullet_list)}(hhh](h list_item)}(h>PGP: https://www.kernel.org/static/files/hardware-security.asch]h)}(hjh](hPGP: }(hjhhhNhNubjz)}(h9https://www.kernel.org/static/files/hardware-security.asch]h9https://www.kernel.org/static/files/hardware-security.asc}(hjhhhNhNubah}(h]h ]h"]h$]h&]refurijuh1jyhjubeh}(h]h ]h"]h$]h&]uh1hhhhK+hjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hBS/MIME: https://www.kernel.org/static/files/hardware-security.crt h]h)}(hAS/MIME: https://www.kernel.org/static/files/hardware-security.crth](hS/MIME: }(hjhhhNhNubjz)}(h9https://www.kernel.org/static/files/hardware-security.crth]h9https://www.kernel.org/static/files/hardware-security.crt}(hjhhhNhNubah}(h]h ]h"]h$]h&]refurijuh1jyhjubeh}(h]h ]h"]h$]h&]uh1hhhhK,hjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]bullet-uh1jhhhK+hjubah}(h]h ]h"]h$]h&]uh1jhhhK+hjhhubh)}(hWhile hardware security issues are often handled by the affected silicon vendor, we welcome contact from researchers or individuals who have identified a potential hardware flaw.h]hWhile hardware security issues are often handled by the affected silicon vendor, we welcome contact from researchers or individuals who have identified a potential hardware flaw.}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK.hjhhubh)}(hhh](h)}(hHardware security officersh]hHardware security officers}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhK3ubh)}(h/The current team of hardware security officers:h]h/The current team of hardware security officers:}(hj*hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK5hjhhubj)}(h- Linus Torvalds (Linux Foundation Fellow) - Greg Kroah-Hartman (Linux Foundation Fellow) - Thomas Gleixner (Linux Foundation Fellow) h]j)}(hhh](j)}(h(Linus Torvalds (Linux Foundation Fellow)h]h)}(hjAh]h(Linus Torvalds (Linux Foundation Fellow)}(hjChhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK7hj?ubah}(h]h ]h"]h$]h&]uh1jhj<ubj)}(h,Greg Kroah-Hartman (Linux Foundation Fellow)h]h)}(hjXh]h,Greg Kroah-Hartman (Linux Foundation Fellow)}(hjZhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK8hjVubah}(h]h ]h"]h$]h&]uh1jhj<ubj)}(h*Thomas Gleixner (Linux Foundation Fellow) h]h)}(h)Thomas Gleixner (Linux Foundation Fellow)h]h)Thomas Gleixner (Linux Foundation Fellow)}(hjqhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK9hjmubah}(h]h ]h"]h$]h&]uh1jhj<ubeh}(h]h ]h"]h$]h&]jjuh1jhhhK7hj8ubah}(h]h ]h"]h$]h&]uh1jhhhK7hjhhubeh}(h]hardware-security-officersah ]h"]hardware security officersah$]h&]uh1hhjhhhhhK3ubh)}(hhh](h)}(hOperation of mailing-listsh]hOperation of mailing-lists}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhKhjhhubh)}(h]The Linux Foundation's current director of IT Project infrastructure is Konstantin Ryabitsev.h]h_The Linux Foundation’s current director of IT Project infrastructure is Konstantin Ryabitsev.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKFhjhhubeh}(h]operation-of-mailing-listsah ]h"]operation of mailing-listsah$]h&]uh1hhjhhhhhKhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKbhjhhubh)}(hX{All involved developers pledge to adhere to the embargo rules and to keep the received information confidential. Violation of the pledge will lead to immediate exclusion from the current issue and removal from all related mailing lists. In addition, the hardware security team will also exclude the offender from future issues. The impact of this consequence is a highly effective deterrent in our community. In case a violation happens the hardware security team will inform the involved parties immediately. If you or anyone else becomes aware of a potential violation, please report it immediately to the Hardware security officers.h]hX{All involved developers pledge to adhere to the embargo rules and to keep the received information confidential. Violation of the pledge will lead to immediate exclusion from the current issue and removal from all related mailing lists. In addition, the hardware security team will also exclude the offender from future issues. The impact of this consequence is a highly effective deterrent in our community. In case a violation happens the hardware security team will inform the involved parties immediately. If you or anyone else becomes aware of a potential violation, please report it immediately to the Hardware security officers.}(hjLhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKghjhhubh)}(hhh](h)}(hProcessh]hProcess}(hj]hhhNhNubah}(h]h ]h"]h$]h&]uh1hhjZhhhhhKsubh)}(hXDue to the globally distributed nature of Linux kernel development, face-to-face meetings are almost impossible to address hardware security issues. Phone conferences are hard to coordinate due to time zones and other factors and should be only used when absolutely necessary. Encrypted email has been proven to be the most effective and secure communication method for these types of issues.h]hXDue to the globally distributed nature of Linux kernel development, face-to-face meetings are almost impossible to address hardware security issues. Phone conferences are hard to coordinate due to time zones and other factors and should be only used when absolutely necessary. Encrypted email has been proven to be the most effective and secure communication method for these types of issues.}(hjkhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKuhjZhhubh)}(hhh](h)}(hStart of Disclosureh]hStart of Disclosure}(hj|hhhNhNubah}(h]h ]h"]h$]h&]uh1hhjyhhhhhK}ubh)}(hXDisclosure starts by emailing the Linux kernel hardware security team per the Contact section above. This initial contact should contain a description of the problem and a list of any known affected silicon. If your organization builds or distributes the affected hardware, we encourage you to also consider what other hardware could be affected. The disclosing party is responsible for contacting the affected silicon vendors in a timely manner.h]hXDisclosure starts by emailing the Linux kernel hardware security team per the Contact section above. This initial contact should contain a description of the problem and a list of any known affected silicon. If your organization builds or distributes the affected hardware, we encourage you to also consider what other hardware could be affected. The disclosing party is responsible for contacting the affected silicon vendors in a timely manner.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjyhhubh)}(hThe hardware security team will provide an incident-specific encrypted mailing list which will be used for initial discussion with the reporter, further disclosure, and coordination of fixes.h]hThe hardware security team will provide an incident-specific encrypted mailing list which will be used for initial discussion with the reporter, further disclosure, and coordination of fixes.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjyhhubh)}(hXThe hardware security team will provide the disclosing party a list of developers (domain experts) who should be informed initially about the issue after confirming with the developers that they will adhere to this Memorandum of Understanding and the documented process. These developers form the initial response team and will be responsible for handling the issue after initial contact. The hardware security team is supporting the response team, but is not necessarily involved in the mitigation development process.h]hXThe hardware security team will provide the disclosing party a list of developers (domain experts) who should be informed initially about the issue after confirming with the developers that they will adhere to this Memorandum of Understanding and the documented process. These developers form the initial response team and will be responsible for handling the issue after initial contact. The hardware security team is supporting the response team, but is not necessarily involved in the mitigation development process.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjyhhubh)}(hX#While individual developers might be covered by a non-disclosure agreement via their employer, they cannot enter individual non-disclosure agreements in their role as Linux kernel developers. They will, however, agree to adhere to this documented process and the Memorandum of Understanding.h]hX#While individual developers might be covered by a non-disclosure agreement via their employer, they cannot enter individual non-disclosure agreements in their role as Linux kernel developers. They will, however, agree to adhere to this documented process and the Memorandum of Understanding.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjyhhubh)}(hThe disclosing party should provide a list of contacts for all other entities who have already been, or should be, informed about the issue. This serves several purposes:h]hThe disclosing party should provide a list of contacts for all other entities who have already been, or should be, informed about the issue. This serves several purposes:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjyhhubj)}(hX- The list of disclosed entities allows communication across the industry, e.g. other OS vendors, HW vendors, etc. - The disclosed entities can be contacted to name experts who should participate in the mitigation development. - If an expert who is required to handle an issue is employed by a listed entity or member of an listed entity, then the response teams can request the disclosure of that expert from that entity. This ensures that the expert is also part of the entity's response team. h]j)}(hhh](j)}(hqThe list of disclosed entities allows communication across the industry, e.g. other OS vendors, HW vendors, etc. h]h)}(hpThe list of disclosed entities allows communication across the industry, e.g. other OS vendors, HW vendors, etc.h]hpThe list of disclosed entities allows communication across the industry, e.g. other OS vendors, HW vendors, etc.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hnThe disclosed entities can be contacted to name experts who should participate in the mitigation development. h]h)}(hmThe disclosed entities can be contacted to name experts who should participate in the mitigation development.h]hmThe disclosed entities can be contacted to name experts who should participate in the mitigation development.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hX If an expert who is required to handle an issue is employed by a listed entity or member of an listed entity, then the response teams can request the disclosure of that expert from that entity. This ensures that the expert is also part of the entity's response team. h]h)}(hX If an expert who is required to handle an issue is employed by a listed entity or member of an listed entity, then the response teams can request the disclosure of that expert from that entity. This ensures that the expert is also part of the entity's response team.h]hX If an expert who is required to handle an issue is employed by a listed entity or member of an listed entity, then the response teams can request the disclosure of that expert from that entity. This ensures that the expert is also part of the entity’s response team.}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]jjuh1jhhhKhjubah}(h]h ]h"]h$]h&]uh1jhhhKhjyhhubeh}(h]start-of-disclosureah ]h"]start of disclosureah$]h&]uh1hhjZhhhhhK}ubh)}(hhh](h)}(h Disclosureh]h Disclosure}(hj6hhhNhNubah}(h]h ]h"]h$]h&]uh1hhj3hhhhhKubh)}(hxThe disclosing party provides detailed information to the initial response team via the specific encrypted mailing-list.h]hxThe disclosing party provides detailed information to the initial response team via the specific encrypted mailing-list.}(hjDhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj3hhubh)}(hFrom our experience, the technical documentation of these issues is usually a sufficient starting point, and further technical clarification is best done via email.h]hFrom our experience, the technical documentation of these issues is usually a sufficient starting point, and further technical clarification is best done via email.}(hjRhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj3hhubeh}(h] disclosureah ]h"] disclosureah$]h&]uh1hhjZhhhhhKubh)}(hhh](h)}(hMitigation developmenth]hMitigation development}(hjkhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhhKubh)}(hiThe initial response team sets up an encrypted mailing-list or repurposes an existing one if appropriate.h]hiThe initial response team sets up an encrypted mailing-list or repurposes an existing one if appropriate.}(hjyhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhhubh)}(hUsing a mailing list is close to the normal Linux development process and has been successfully used to develop mitigations for various hardware security issues in the past.h]hUsing a mailing list is close to the normal Linux development process and has been successfully used to develop mitigations for various hardware security issues in the past.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhhubh)}(hXThe mailing list operates in the same way as normal Linux development. Patches are posted, discussed, and reviewed and if agreed upon, applied to a non-public git repository which is only accessible to the participating developers via a secure connection. The repository contains the main development branch against the mainline kernel and backport branches for stable kernel versions as necessary.h]hXThe mailing list operates in the same way as normal Linux development. Patches are posted, discussed, and reviewed and if agreed upon, applied to a non-public git repository which is only accessible to the participating developers via a secure connection. The repository contains the main development branch against the mainline kernel and backport branches for stable kernel versions as necessary.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhhubh)}(hThe initial response team will identify further experts from the Linux kernel developer community as needed. Any involved party can suggest further experts to be included, each of which will be subject to the same requirements outlined above.h]hThe initial response team will identify further experts from the Linux kernel developer community as needed. Any involved party can suggest further experts to be included, each of which will be subject to the same requirements outlined above.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhhubh)}(hqBringing in experts can happen at any time in the development process and needs to be handled in a timely manner.h]hqBringing in experts can happen at any time in the development process and needs to be handled in a timely manner.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhhubh)}(hIf an expert is employed by or a member of an entity on the disclosure list provided by the disclosing party, then participation will be requested from the relevant entity.h]hIf an expert is employed by or a member of an entity on the disclosure list provided by the disclosing party, then participation will be requested from the relevant entity.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhhubh)}(hXIf not, then the disclosing party will be informed about the experts' participation. The experts are covered by the Memorandum of Understanding and the disclosing party is requested to acknowledge their participation. In the case where the disclosing party has a compelling reason to object, any objection must to be raised within five working days and resolved with the incident team immediately. If the disclosing party does not react within five working days this is taken as silent acknowledgment.h]hXIf not, then the disclosing party will be informed about the experts’ participation. The experts are covered by the Memorandum of Understanding and the disclosing party is requested to acknowledge their participation. In the case where the disclosing party has a compelling reason to object, any objection must to be raised within five working days and resolved with the incident team immediately. If the disclosing party does not react within five working days this is taken as silent acknowledgment.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhhubh)}(hAfter the incident team acknowledges or resolves an objection, the expert is disclosed and brought into the development process.h]hAfter the incident team acknowledges or resolves an objection, the expert is disclosed and brought into the development process.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhhubh)}(hList participants may not communicate about the issue outside of the private mailing list. List participants may not use any shared resources (e.g. employer build farms, CI systems, etc) when working on patches.h]hList participants may not communicate about the issue outside of the private mailing list. List participants may not use any shared resources (e.g. employer build farms, CI systems, etc) when working on patches.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhhubeh}(h]mitigation-developmentah ]h"]mitigation developmentah$]h&]uh1hhjZhhhhhKubh)}(hhh](h)}(h Early accessh]h Early access}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhKubh)}(hThe patches discussed and developed on the list can neither be distributed to any individual who is not a member of the response team nor to any other organization.h]hThe patches discussed and developed on the list can neither be distributed to any individual who is not a member of the response team nor to any other organization.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubh)}(hTo allow the affected silicon vendors to work with their internal teams and industry partners on testing, validation, and logistics, the following exception is provided:h]hTo allow the affected silicon vendors to work with their internal teams and industry partners on testing, validation, and logistics, the following exception is provided:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubj)}(hX#Designated representatives of the affected silicon vendors are allowed to hand over the patches at any time to the silicon vendor’s response team. The representative must notify the kernel response team about the handover. The affected silicon vendor must have and maintain their own documented security process for any patches shared with their response team that is consistent with this policy. The silicon vendor’s response team can distribute these patches to their industry partners and to their internal teams under the silicon vendor’s documented security process. Feedback from the industry partners goes back to the silicon vendor and is communicated by the silicon vendor to the kernel response team. The handover to the silicon vendor’s response team removes any responsibility or liability from the kernel response team regarding premature disclosure, which happens due to the involvement of the silicon vendor’s internal teams or industry partners. The silicon vendor guarantees this release of liability by agreeing to this process. h](h)}(hXDesignated representatives of the affected silicon vendors are allowed to hand over the patches at any time to the silicon vendor’s response team. The representative must notify the kernel response team about the handover. The affected silicon vendor must have and maintain their own documented security process for any patches shared with their response team that is consistent with this policy.h]hXDesignated representatives of the affected silicon vendors are allowed to hand over the patches at any time to the silicon vendor’s response team. The representative must notify the kernel response team about the handover. The affected silicon vendor must have and maintain their own documented security process for any patches shared with their response team that is consistent with this policy.}(hj0hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj,ubh)}(hX=The silicon vendor’s response team can distribute these patches to their industry partners and to their internal teams under the silicon vendor’s documented security process. Feedback from the industry partners goes back to the silicon vendor and is communicated by the silicon vendor to the kernel response team.h]hX=The silicon vendor’s response team can distribute these patches to their industry partners and to their internal teams under the silicon vendor’s documented security process. Feedback from the industry partners goes back to the silicon vendor and is communicated by the silicon vendor to the kernel response team.}(hj>hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj,ubh)}(hXSThe handover to the silicon vendor’s response team removes any responsibility or liability from the kernel response team regarding premature disclosure, which happens due to the involvement of the silicon vendor’s internal teams or industry partners. The silicon vendor guarantees this release of liability by agreeing to this process.h]hXSThe handover to the silicon vendor’s response team removes any responsibility or liability from the kernel response team regarding premature disclosure, which happens due to the involvement of the silicon vendor’s internal teams or industry partners. The silicon vendor guarantees this release of liability by agreeing to this process.}(hjLhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj,ubeh}(h]h ]h"]h$]h&]uh1jhhhKhjhhubeh}(h] early-accessah ]h"] early accessah$]h&]uh1hhjZhhhhhKubh)}(hhh](h)}(hCoordinated releaseh]hCoordinated release}(hjkhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhhKubh)}(hXThe involved parties will negotiate the date and time when the embargo ends. At that point, the prepared mitigations are published into the relevant kernel trees. There is no pre-notification process: the mitigations are published in public and available to everyone at the same time.h]hXThe involved parties will negotiate the date and time when the embargo ends. At that point, the prepared mitigations are published into the relevant kernel trees. There is no pre-notification process: the mitigations are published in public and available to everyone at the same time.}(hjyhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhhubh)}(hX!While we understand that hardware security issues need coordinated embargo time, the embargo time should be constrained to the minimum time that is required for all involved parties to develop, test, and prepare their mitigations. Extending embargo time artificially to meet conference talk dates or other non-technical reasons creates more work and burden for the involved developers and response teams as the patches need to be kept up to date in order to follow the ongoing upstream kernel development, which might create conflicting changes.h]hX!While we understand that hardware security issues need coordinated embargo time, the embargo time should be constrained to the minimum time that is required for all involved parties to develop, test, and prepare their mitigations. Extending embargo time artificially to meet conference talk dates or other non-technical reasons creates more work and burden for the involved developers and response teams as the patches need to be kept up to date in order to follow the ongoing upstream kernel development, which might create conflicting changes.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhhubeh}(h]coordinated-releaseah ]h"]coordinated releaseah$]h&]uh1hhjZhhhhhKubh)}(hhh](h)}(hCVE assignmenth]hCVE assignment}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhMubh)}(hNeither the hardware security team nor the initial response team assign CVEs, nor are CVEs required for the development process. If CVEs are provided by the disclosing party they can be used for documentation purposes.h]hNeither the hardware security team nor the initial response team assign CVEs, nor are CVEs required for the development process. If CVEs are provided by the disclosing party they can be used for documentation purposes.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubeh}(h]cve-assignmentah ]h"]cve assignmentah$]h&]uh1hhjZhhhhhMubeh}(h]processah ]h"]processah$]h&]uh1hhjhhhhhKsubeh}(h]memorandum-of-understandingah ]h"]memorandum of understandingah$]h&]uh1hhhhhhhhKTubh)}(hhh](h)}(hProcess ambassadorsh]hProcess ambassadors}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhMubh)}(hXgFor assistance with this process we have established ambassadors in various organizations, who can answer questions about or provide guidance on the reporting process and further handling. Ambassadors are not involved in the disclosure of a particular issue, unless requested by a response team or by an involved disclosed party. The current ambassadors list:h]hXgFor assistance with this process we have established ambassadors in various organizations, who can answer questions about or provide guidance on the reporting process and further handling. Ambassadors are not involved in the disclosure of a particular issue, unless requested by a response team or by an involved disclosed party. The current ambassadors list:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubj)}(hX]============= ======================================================== AMD Tom Lendacky Ampere Darren Hart ARM Catalin Marinas IBM Power Madhavan Srinivasan IBM Z Christian Borntraeger Intel Tony Luck Qualcomm Trilok Soni RISC-V Palmer Dabbelt Samsung Javier González Microsoft James Morris Xen Andrew Cooper Canonical John Johansen Debian Ben Hutchings Oracle Konrad Rzeszutek Wilk Red Hat Josh Poimboeuf SUSE Jiri Kosina Google Kees Cook LLVM Nick Desaulniers ============= ======================================================== h]htable)}(hhh]htgroup)}(hhh](hcolspec)}(hhh]h}(h]h ]h"]h$]h&]colwidthK uh1jhjubj)}(hhh]h}(h]h ]h"]h$]h&]colwidthK8uh1jhjubhtbody)}(hhh](hrow)}(hhh](hentry)}(hhh]h)}(hAMDh]hAMD}(hj&hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM"hj#ubah}(h]h ]h"]h$]h&]uh1j!hjubj")}(hhh]h)}(h&Tom Lendacky h](hTom Lendacky <}(hj=hhhNhNubjz)}(hthomas.lendacky@amd.comh]hthomas.lendacky@amd.com}(hjEhhhNhNubah}(h]h ]h"]h$]h&]refurimailto:thomas.lendacky@amd.comuh1jyhj=ubh>}(hj=hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhM"hj:ubah}(h]h ]h"]h$]h&]uh1j!hjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j")}(hhh]h)}(hAmpereh]hAmpere}(hjqhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM#hjnubah}(h]h ]h"]h$]h&]uh1j!hjkubj")}(hhh]h)}(h+Darren Hart h](h Darren Hart <}(hjhhhNhNubjz)}(hdarren@os.amperecomputing.comh]hdarren@os.amperecomputing.com}(hjhhhNhNubah}(h]h ]h"]h$]h&]refuri$mailto:darren@os.amperecomputing.comuh1jyhjubh>}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhM#hjubah}(h]h ]h"]h$]h&]uh1j!hjkubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j")}(hhh]h)}(hARMh]hARM}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM$hjubah}(h]h ]h"]h$]h&]uh1j!hjubj")}(hhh]h)}(h)Catalin Marinas h](hCatalin Marinas <}(hjhhhNhNubjz)}(hcatalin.marinas@arm.comh]hcatalin.marinas@arm.com}(hjhhhNhNubah}(h]h ]h"]h$]h&]refurimailto:catalin.marinas@arm.comuh1jyhjubh>}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhM$hjubah}(h]h ]h"]h$]h&]uh1j!hjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j")}(hhh]h)}(h IBM Powerh]h IBM Power}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM%hjubah}(h]h ]h"]h$]h&]uh1j!hjubj")}(hhh]h)}(h)Madhavan Srinivasan h](hMadhavan Srinivasan <}(hjhhhNhNubjz)}(hmaddy@linux.ibm.comh]hmaddy@linux.ibm.com}(hj&hhhNhNubah}(h]h ]h"]h$]h&]refurimailto:maddy@linux.ibm.comuh1jyhjubh>}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhM%hjubah}(h]h ]h"]h$]h&]uh1j!hjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j")}(hhh]h)}(hIBM Zh]hIBM Z}(hjRhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM&hjOubah}(h]h ]h"]h$]h&]uh1j!hjLubj")}(hhh]h)}(h.Christian Borntraeger h](hChristian Borntraeger <}(hjihhhNhNubjz)}(hborntraeger@de.ibm.comh]hborntraeger@de.ibm.com}(hjqhhhNhNubah}(h]h ]h"]h$]h&]refurimailto:borntraeger@de.ibm.comuh1jyhjiubh>}(hjihhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhM&hjfubah}(h]h ]h"]h$]h&]uh1j!hjLubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j")}(hhh]h)}(hIntelh]hIntel}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM'hjubah}(h]h ]h"]h$]h&]uh1j!hjubj")}(hhh]h)}(hTony Luck h](h Tony Luck <}(hjhhhNhNubjz)}(htony.luck@intel.comh]htony.luck@intel.com}(hjhhhNhNubah}(h]h ]h"]h$]h&]refurimailto:tony.luck@intel.comuh1jyhjubh>}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhM'hjubah}(h]h ]h"]h$]h&]uh1j!hjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j")}(hhh]h)}(hQualcommh]hQualcomm}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM(hjubah}(h]h ]h"]h$]h&]uh1j!hjubj")}(hhh]h)}(h$Trilok Soni h](h Trilok Soni <}(hjhhhNhNubjz)}(hquic_tsoni@quicinc.comh]hquic_tsoni@quicinc.com}(hjhhhNhNubah}(h]h ]h"]h$]h&]refurimailto:quic_tsoni@quicinc.comuh1jyhjubh>}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhM(hjubah}(h]h ]h"]h$]h&]uh1j!hjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j")}(hhh]h)}(hRISC-Vh]hRISC-V}(hj3hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM)hj0ubah}(h]h ]h"]h$]h&]uh1j!hj-ubj")}(hhh]h)}(h#Palmer Dabbelt h](hPalmer Dabbelt <}(hjJhhhNhNubjz)}(hpalmer@dabbelt.comh]hpalmer@dabbelt.com}(hjRhhhNhNubah}(h]h ]h"]h$]h&]refurimailto:palmer@dabbelt.comuh1jyhjJubh>}(hjJhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhM)hjGubah}(h]h ]h"]h$]h&]uh1j!hj-ubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j")}(hhh]h)}(hSamsungh]hSamsung}(hj~hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM*hj{ubah}(h]h ]h"]h$]h&]uh1j!hjxubj")}(hhh]h)}(h*Javier González h](hJavier González <}(hjhhhNhNubjz)}(hjavier.gonz@samsung.comh]hjavier.gonz@samsung.com}(hjhhhNhNubah}(h]h ]h"]h$]h&]refurimailto:javier.gonz@samsung.comuh1jyhjubh>}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhM*hjubah}(h]h ]h"]h$]h&]uh1j!hjxubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j")}(hhh]h)}(h Microsofth]h Microsoft}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM,hjubah}(h]h ]h"]h$]h&]uh1j!hjubj")}(hhh]h)}(h+James Morris h](hJames Morris <}(hjhhhNhNubjz)}(hjamorris@linux.microsoft.comh]hjamorris@linux.microsoft.com}(hjhhhNhNubah}(h]h ]h"]h$]h&]refuri#mailto:jamorris@linux.microsoft.comuh1jyhjubh>}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhM,hjubah}(h]h ]h"]h$]h&]uh1j!hjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j")}(hhh]h)}(hXenh]hXen}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM-hj ubah}(h]h ]h"]h$]h&]uh1j!hj ubj")}(hhh]h)}(h)Andrew Cooper h](hAndrew Cooper <}(hj+ hhhNhNubjz)}(handrew.cooper3@citrix.comh]handrew.cooper3@citrix.com}(hj3 hhhNhNubah}(h]h ]h"]h$]h&]refuri mailto:andrew.cooper3@citrix.comuh1jyhj+ ubh>}(hj+ hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhM-hj( ubah}(h]h ]h"]h$]h&]uh1j!hj ubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j")}(hhh]h)}(h Canonicalh]h Canonical}(hj_ hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM/hj\ ubah}(h]h ]h"]h$]h&]uh1j!hjY ubj")}(hhh]h)}(h+John Johansen h](hJohn Johansen <}(hjv hhhNhNubjz)}(hjohn.johansen@canonical.comh]hjohn.johansen@canonical.com}(hj~ hhhNhNubah}(h]h ]h"]h$]h&]refuri"mailto:john.johansen@canonical.comuh1jyhjv ubh>}(hjv hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhM/hjs ubah}(h]h ]h"]h$]h&]uh1j!hjY ubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j")}(hhh]h)}(hDebianh]hDebian}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM0hj ubah}(h]h ]h"]h$]h&]uh1j!hj ubj")}(hhh]h)}(h#Ben Hutchings h](hBen Hutchings <}(hj hhhNhNubjz)}(hben@decadent.org.ukh]hben@decadent.org.uk}(hj hhhNhNubah}(h]h ]h"]h$]h&]refurimailto:ben@decadent.org.ukuh1jyhj ubh>}(hj hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhM0hj ubah}(h]h ]h"]h$]h&]uh1j!hj ubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j")}(hhh]h)}(hOracleh]hOracle}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM1hj ubah}(h]h ]h"]h$]h&]uh1j!hj ubj")}(hhh]h)}(h.Konrad Rzeszutek Wilk h](hKonrad Rzeszutek Wilk <}(hj hhhNhNubjz)}(hkonrad.wilk@oracle.comh]hkonrad.wilk@oracle.com}(hj hhhNhNubah}(h]h ]h"]h$]h&]refurimailto:konrad.wilk@oracle.comuh1jyhj ubh>}(hj hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhM1hj ubah}(h]h ]h"]h$]h&]uh1j!hj ubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j")}(hhh]h)}(hRed Hath]hRed Hat}(hj@ hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM2hj= ubah}(h]h ]h"]h$]h&]uh1j!hj: ubj")}(hhh]h)}(h$Josh Poimboeuf h](hJosh Poimboeuf <}(hjW hhhNhNubjz)}(hjpoimboe@redhat.comh]hjpoimboe@redhat.com}(hj_ hhhNhNubah}(h]h ]h"]h$]h&]refurimailto:jpoimboe@redhat.comuh1jyhjW ubh>}(hjW hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhM2hjT ubah}(h]h ]h"]h$]h&]uh1j!hj: ubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j")}(hhh]h)}(hSUSEh]hSUSE}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM3hj ubah}(h]h ]h"]h$]h&]uh1j!hj ubj")}(hhh]h)}(hJiri Kosina h](h Jiri Kosina <}(hj hhhNhNubjz)}(hjkosina@suse.czh]hjkosina@suse.cz}(hj hhhNhNubah}(h]h ]h"]h$]h&]refurimailto:jkosina@suse.czuh1jyhj ubh>}(hj hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhM3hj ubah}(h]h ]h"]h$]h&]uh1j!hj ubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j")}(hhh]h)}(hGoogleh]hGoogle}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM5hj ubah}(h]h ]h"]h$]h&]uh1j!hj ubj")}(hhh]h)}(h!Kees Cook h](h Kees Cook <}(hj hhhNhNubjz)}(hkeescook@chromium.orgh]hkeescook@chromium.org}(hj hhhNhNubah}(h]h ]h"]h$]h&]refurimailto:keescook@chromium.orguh1jyhj ubh>}(hj hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhM5hj ubah}(h]h ]h"]h$]h&]uh1j!hj ubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j")}(hhh]h)}(hLLVMh]hLLVM}(hj! hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM7hj ubah}(h]h ]h"]h$]h&]uh1j!hj ubj")}(hhh]h)}(h*Nick Desaulniers h](hNick Desaulniers <}(hj8 hhhNhNubjz)}(hndesaulniers@google.comh]hndesaulniers@google.com}(hj@ hhhNhNubah}(h]h ]h"]h$]h&]refurimailto:ndesaulniers@google.comuh1jyhj8 ubh>}(hj8 hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhM7hj5 ubah}(h]h ]h"]h$]h&]uh1j!hj ubeh}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]colsKuh1jhjubah}(h]h ]h"]h$]h&]uh1jhjubah}(h]h ]h"]h$]h&]uh1jhhhM!hjhhubh)}(hIf you want your organization to be added to the ambassadors list, please contact the hardware security team. The nominated ambassador has to understand and support our process fully and is ideally well-connected in the Linux kernel community.h]hIf you want your organization to be added to the ambassadors list, please contact the hardware security team. The nominated ambassador has to understand and support our process fully and is ideally well-connected in the Linux kernel community.}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM:hjhhubeh}(h]process-ambassadorsah ]h"]process ambassadorsah$]h&]uh1hhhhhhhhMubh)}(hhh](h)}(hEncrypted mailing-listsh]hEncrypted mailing-lists}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhj hhhhhM@ubh)}(hX"We use encrypted mailing lists for communication. The operating principle of these lists is that email sent to the list is encrypted either with the list's PGP key or with the list's S/MIME certificate. The mailing list software decrypts the email and re-encrypts it individually for each subscriber with the subscriber's PGP key or S/MIME certificate. Details about the mailing list software and the setup that is used to ensure the security of the lists and protection of the data can be found here: https://korg.wiki.kernel.org/userdoc/remail.h](hXWe use encrypted mailing lists for communication. The operating principle of these lists is that email sent to the list is encrypted either with the list’s PGP key or with the list’s S/MIME certificate. The mailing list software decrypts the email and re-encrypts it individually for each subscriber with the subscriber’s PGP key or S/MIME certificate. Details about the mailing list software and the setup that is used to ensure the security of the lists and protection of the data can be found here: }(hj hhhNhNubjz)}(h+https://korg.wiki.kernel.org/userdoc/remailh]h+https://korg.wiki.kernel.org/userdoc/remail}(hj hhhNhNubah}(h]h ]h"]h$]h&]refurij uh1jyhj ubh.}(hj hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhMBhj hhubh)}(hhh](h)}(h List keysh]h List keys}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhj hhhhhMLubh)}(hFor initial contact see the :ref:`Contact` section above. For incident specific mailing lists, the key and S/MIME certificate are conveyed to the subscribers by email sent from the specific list.h](hFor initial contact see the }(hj hhhNhNubh)}(h:ref:`Contact`h]jG)}(hj h]hContact}(hj hhhNhNubah}(h]h ](jRstdstd-refeh"]h$]h&]uh1jFhj ubah}(h]h ]h"]h$]h&]refdocj_ refdomainj reftyperef refexplicitrefwarnjecontactuh1hhhhMNhj ubh section above. For incident specific mailing lists, the key and S/MIME certificate are conveyed to the subscribers by email sent from the specific list.}(hj hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhMNhj hhubeh}(h] list-keysah ]h"] list keysah$]h&]uh1hhj hhhhhMLubh)}(hhh](h)}(h'Subscription to incident-specific listsh]h'Subscription to incident-specific lists}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhj hhhhhMSubh)}(hSubscription to incident-specific lists is handled by the response teams. Disclosed parties who want to participate in the communication send a list of potential experts to the response team so the response team can validate subscription requests.h]hSubscription to incident-specific lists is handled by the response teams. Disclosed parties who want to participate in the communication send a list of potential experts to the response team so the response team can validate subscription requests.}(hj# hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMUhj hhubh)}(hXWEach subscriber needs to send a subscription request to the response team by email. The email must be signed with the subscriber's PGP key or S/MIME certificate. If a PGP key is used, it must be available from a public key server and is ideally connected to the Linux kernel's PGP web of trust. See also: https://www.kernel.org/signature.html.h](hX5Each subscriber needs to send a subscription request to the response team by email. The email must be signed with the subscriber’s PGP key or S/MIME certificate. If a PGP key is used, it must be available from a public key server and is ideally connected to the Linux kernel’s PGP web of trust. See also: }(hj1 hhhNhNubjz)}(h%https://www.kernel.org/signature.htmlh]h%https://www.kernel.org/signature.html}(hj9 hhhNhNubah}(h]h ]h"]h$]h&]refurij; uh1jyhj1 ubh.}(hj1 hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhMZhj hhubh)}(hXThe response team verifies that the subscriber request is valid and adds the subscriber to the list. After subscription the subscriber will receive email from the mailing-list which is signed either with the list's PGP key or the list's S/MIME certificate. The subscriber's email client can extract the PGP key or the S/MIME certificate from the signature so the subscriber can send encrypted email to the list.h]hXThe response team verifies that the subscriber request is valid and adds the subscriber to the list. After subscription the subscriber will receive email from the mailing-list which is signed either with the list’s PGP key or the list’s S/MIME certificate. The subscriber’s email client can extract the PGP key or the S/MIME certificate from the signature so the subscriber can send encrypted email to the list.}(hjR hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM`hj hhubeh}(h]'subscription-to-incident-specific-listsah ]h"]'subscription to incident-specific listsah$]h&]uh1hhj hhhhhMSubeh}(h]encrypted-mailing-listsah ]h"]encrypted mailing-listsah$]h&]uh1hhhhhhhhM@ubeh}(h](hŒid1eh ]h"](embargoed hardware issuesembargoed_hardware_issueseh$]h&]uh1hhhhhhhhKj}jv hsj}hhsubeh}(h]h ]h"]h$]h&]sourcehuh1hcurrent_sourceN current_lineNsettingsdocutils.frontendValues)}(hN generatorN datestampN source_linkN source_urlN toc_backlinksj!footnote_backlinksK sectnum_xformKstrip_commentsNstrip_elements_with_classesN strip_classesN report_levelK halt_levelKexit_status_levelKdebugNwarning_streamN tracebackinput_encoding utf-8-siginput_encoding_error_handlerstrictoutput_encodingutf-8output_encoding_error_handlerj error_encodingutf-8error_encoding_error_handlerbackslashreplace language_codeenrecord_dependenciesNconfigN id_prefixhauto_id_prefixid dump_settingsNdump_internalsNdump_transformsNdump_pseudo_xmlNexpose_internalsNstrict_visitorN_disable_configN_sourcehÌ _destinationN _config_files]7/var/lib/git/docbuild/linux/Documentation/docutils.confafile_insertion_enabled raw_enabledKline_length_limitM'pep_referencesN pep_base_urlhttps://peps.python.org/pep_file_url_templatepep-%04drfc_referencesN rfc_base_url&https://datatracker.ietf.org/doc/html/ tab_widthKtrim_footnote_reference_spacesyntax_highlightlong smart_quotessmartquotes_locales]character_level_inline_markupdoctitle_xform docinfo_xformKsectsubtitle_xform image_loadinglinkembed_stylesheetcloak_email_addressessection_self_linkenvNubreporterNindirect_targets]substitution_defs}substitution_names}refnames}refids}(h]haj]jaunameids}(jv hju jr jjjjjjjjjjjjjjj0j-jejbjjjejbjjjjj j jm jj j j je jb u nametypes}(jv ju jjjjjjjj0jejjejjj jm j je uh}(hhjr hjhjjjjjjjjjjjjjjZj-jyjbj3jjhjbjjjhjjj jjj j j j jb j u footnote_refs} citation_refs} autofootnotes]autofootnote_refs]symbol_footnotes]symbol_footnote_refs] footnotes] citations]autofootnote_startKsymbol_footnote_startK id_counter collectionsCounter}j KsRparse_messages]hsystem_message)}(hhh]h)}(h*Duplicate implicit target name: "contact".h]h.Duplicate implicit target name: “contact”.}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhj ubah}(h]h ]h"]h$]h&]jalevelKtypeINFOsourcehÌlineKuh1j hjhhhhhKubatransform_messages](j )}(hhh]h)}(hhh]h?Hyperlink target "embargoed-hardware-issues" is not referenced.}hj$ sbah}(h]h ]h"]h$]h&]uh1hhj! ubah}(h]h ]h"]h$]h&]levelKtypej sourcehÌlineKuh1j ubj )}(hhh]h)}(hhh]h-Hyperlink target "contact" is not referenced.}hj> sbah}(h]h ]h"]h$]h&]uh1hhj; ubah}(h]h ]h"]h$]h&]levelKtypej sourcehÌlineKuh1j ube transformerN include_log] decorationNhhub.