€•RŒsphinx.addnodes”Œdocument”“”)”}”(Œ rawsource”Œ”Œchildren”]”(Œ translations”Œ LanguagesNode”“”)”}”(hhh]”(hŒ pending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ refdomain”Œstd”Œreftype”Œdoc”Œ reftarget”Œ-/translations/zh_CN/security/tpm/xen-tpmfront”Œmodname”NŒ classname”NŒ refexplicit”ˆuŒtagname”hhh ubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ-/translations/zh_TW/security/tpm/xen-tpmfront”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ-/translations/it_IT/security/tpm/xen-tpmfront”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ-/translations/ja_JP/security/tpm/xen-tpmfront”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ-/translations/ko_KR/security/tpm/xen-tpmfront”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒSpanish”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ-/translations/sp_SP/security/tpm/xen-tpmfront”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h hhŒ _document”hŒsource”NŒline”NubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒVirtual TPM interface for Xen”h]”hŒVirtual TPM interface for Xen”…””}”(hh¨hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hh£hžhhŸŒG/var/lib/git/docbuild/linux/Documentation/security/tpm/xen-tpmfront.rst”h KubhŒ paragraph”“”)”}”(hŒ;Authors: Matthew Fioravante (JHUAPL), Daniel De Graaf (NSA)”h]”hŒ;Authors: Matthew Fioravante (JHUAPL), Daniel De Graaf (NSA)”…””}”(hh¹hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khh£hžhubh¸)”}”(hŒàThis document describes the virtual Trusted Platform Module (vTPM) subsystem for Xen. The reader is assumed to have familiarity with building and installing Xen, Linux, and a basic understanding of the TPM and vTPM concepts.”h]”hŒàThis document describes the virtual Trusted Platform Module (vTPM) subsystem for Xen. The reader is assumed to have familiarity with building and installing Xen, Linux, and a basic understanding of the TPM and vTPM concepts.”…””}”(hhÇhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khh£hžhubh¢)”}”(hhh]”(h§)”}”(hŒ Introduction”h]”hŒ Introduction”…””}”(hhØhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hhÕhžhhŸh¶h K ubh¸)”}”(hXEThe goal of this work is to provide a TPM functionality to a virtual guest operating system (in Xen terms, a DomU). This allows programs to interact with a TPM in a virtual system the same way they interact with a TPM on the physical system. Each guest gets its own unique, emulated, software TPM. However, each of the vTPM's secrets (Keys, NVRAM, etc) are managed by a vTPM Manager domain, which seals the secrets to the Physical TPM. If the process of creating each of these domains (manager, vTPM, and guest) is trusted, the vTPM subsystem extends the chain of trust rooted in the hardware TPM to virtual machines in Xen. Each major component of vTPM is implemented as a separate domain, providing secure separation guaranteed by the hypervisor. The vTPM domains are implemented in mini-os to reduce memory and processor overhead.”h]”hXGThe goal of this work is to provide a TPM functionality to a virtual guest operating system (in Xen terms, a DomU). This allows programs to interact with a TPM in a virtual system the same way they interact with a TPM on the physical system. Each guest gets its own unique, emulated, software TPM. However, each of the vTPM’s secrets (Keys, NVRAM, etc) are managed by a vTPM Manager domain, which seals the secrets to the Physical TPM. If the process of creating each of these domains (manager, vTPM, and guest) is trusted, the vTPM subsystem extends the chain of trust rooted in the hardware TPM to virtual machines in Xen. Each major component of vTPM is implemented as a separate domain, providing secure separation guaranteed by the hypervisor. The vTPM domains are implemented in mini-os to reduce memory and processor overhead.”…””}”(hhæhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KhhÕhžhubh¸)”}”(hŒiThis mini-os vTPM subsystem was built on top of the previous vTPM work done by IBM and Intel corporation.”h]”hŒiThis mini-os vTPM subsystem was built on top of the previous vTPM work done by IBM and Intel corporation.”…””}”(hhôhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KhhÕhžhubeh}”(h]”Œ introduction”ah ]”h"]”Œ introduction”ah$]”h&]”uh1h¡hh£hžhhŸh¶h K ubh¢)”}”(hhh]”(h§)”}”(hŒDesign Overview”h]”hŒDesign Overview”…””}”(hj hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj hžhhŸh¶h Kubh¸)”}”(hŒ-The architecture of vTPM is described below::”h]”hŒ,The architecture of vTPM is described below:”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K!hj hžhubhŒ literal_block”“”)”}”(hXŒ+------------------+ | Linux DomU | ... | | ^ | | v | | | xen-tpmfront | +------------------+ | ^ v | +------------------+ | mini-os/tpmback | | | ^ | | v | | | vtpm-stubdom | ... | | ^ | | v | | | mini-os/tpmfront | +------------------+ | ^ v | +------------------+ | mini-os/tpmback | | | ^ | | v | | | vtpmmgr-stubdom | | | ^ | | v | | | mini-os/tpm_tis | +------------------+ | ^ v | +------------------+ | Hardware TPM | +------------------+”h]”hXŒ+------------------+ | Linux DomU | ... | | ^ | | v | | | xen-tpmfront | +------------------+ | ^ v | +------------------+ | mini-os/tpmback | | | ^ | | v | | | vtpm-stubdom | ... | | ^ | | v | | | mini-os/tpmfront | +------------------+ | ^ v | +------------------+ | mini-os/tpmback | | | ^ | | v | | | vtpmmgr-stubdom | | | ^ | | v | | | mini-os/tpm_tis | +------------------+ | ^ v | +------------------+ | Hardware TPM | +------------------+”…””}”hj+sbah}”(h]”h ]”h"]”h$]”h&]”Œ xml:space”Œpreserve”uh1j)hŸh¶h K#hj hžhubhŒ bullet_list”“”)”}”(hhh]”(hŒ list_item”“”)”}”(hŒ{Linux DomU: The Linux based guest that wants to use a vTPM. There may be more than one of these. ”h]”hŒdefinition_list”“”)”}”(hhh]”hŒdefinition_list_item”“”)”}”(hŒaLinux DomU: The Linux based guest that wants to use a vTPM. There may be more than one of these. ”h]”(hŒterm”“”)”}”(hŒ Linux DomU:”h]”hŒ Linux DomU:”…””}”(hjShžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jQhŸh¶h KGhjMubhŒ definition”“”)”}”(hhh]”h¸)”}”(hŒTThe Linux based guest that wants to use a vTPM. There may be more than one of these.”h]”hŒTThe Linux based guest that wants to use a vTPM. There may be more than one of these.”…””}”(hjfhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KFhjcubah}”(h]”h ]”h"]”h$]”h&]”uh1jahjMubeh}”(h]”h ]”h"]”h$]”h&]”uh1jKhŸh¶h KGhjHubah}”(h]”h ]”h"]”h$]”h&]”uh1jFhjBubah}”(h]”h ]”h"]”h$]”h&]”uh1j@hj=hžhhŸNh NubjA)”}”(hŒ—xen-tpmfront.ko: Linux kernel virtual TPM frontend driver. This driver provides vTPM access to a Linux-based DomU. ”h]”jG)”}”(hhh]”jL)”}”(hŒsxen-tpmfront.ko: Linux kernel virtual TPM frontend driver. This driver provides vTPM access to a Linux-based DomU. ”h]”(jR)”}”(hŒxen-tpmfront.ko:”h]”hŒxen-tpmfront.ko:”…””}”(hj—hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jQhŸh¶h KKhj“ubjb)”}”(hhh]”h¸)”}”(hŒaLinux kernel virtual TPM frontend driver. This driver provides vTPM access to a Linux-based DomU.”h]”hŒaLinux kernel virtual TPM frontend driver. This driver provides vTPM access to a Linux-based DomU.”…””}”(hj¨hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KJhj¥ubah}”(h]”h ]”h"]”h$]”h&]”uh1jahj“ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jKhŸh¶h KKhjubah}”(h]”h ]”h"]”h$]”h&]”uh1jFhjŒubah}”(h]”h ]”h"]”h$]”h&]”uh1j@hj=hžhhŸNh NubjA)”}”(hX?mini-os/tpmback: Mini-os TPM backend driver. The Linux frontend driver connects to this backend driver to facilitate communications between the Linux DomU and its vTPM. This driver is also used by vtpmmgr-stubdom to communicate with vtpm-stubdom. ”h]”jG)”}”(hhh]”jL)”}”(hŒ÷mini-os/tpmback: Mini-os TPM backend driver. The Linux frontend driver connects to this backend driver to facilitate communications between the Linux DomU and its vTPM. This driver is also used by vtpmmgr-stubdom to communicate with vtpm-stubdom. ”h]”(jR)”}”(hŒmini-os/tpmback:”h]”hŒmini-os/tpmback:”…””}”(hjÙhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jQhŸh¶h KQhjÕubjb)”}”(hhh]”h¸)”}”(hŒåMini-os TPM backend driver. The Linux frontend driver connects to this backend driver to facilitate communications between the Linux DomU and its vTPM. This driver is also used by vtpmmgr-stubdom to communicate with vtpm-stubdom.”h]”hŒåMini-os TPM backend driver. The Linux frontend driver connects to this backend driver to facilitate communications between the Linux DomU and its vTPM. This driver is also used by vtpmmgr-stubdom to communicate with vtpm-stubdom.”…””}”(hjêhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KNhjçubah}”(h]”h ]”h"]”h$]”h&]”uh1jahjÕubeh}”(h]”h ]”h"]”h$]”h&]”uh1jKhŸh¶h KQhjÒubah}”(h]”h ]”h"]”h$]”h&]”uh1jFhjÎubah}”(h]”h ]”h"]”h$]”h&]”uh1j@hj=hžhhŸNh NubjA)”}”(hX5vtpm-stubdom: A mini-os stub domain that implements a vTPM. There is a one to one mapping between running vtpm-stubdom instances and logical vtpms on the system. The vTPM Platform Configuration Registers (PCRs) are normally all initialized to zero. ”h]”jG)”}”(hhh]”jL)”}”(hŒùvtpm-stubdom: A mini-os stub domain that implements a vTPM. There is a one to one mapping between running vtpm-stubdom instances and logical vtpms on the system. The vTPM Platform Configuration Registers (PCRs) are normally all initialized to zero. ”h]”(jR)”}”(hŒ vtpm-stubdom:”h]”hŒ vtpm-stubdom:”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jQhŸh¶h KWhjubjb)”}”(hhh]”h¸)”}”(hŒêA mini-os stub domain that implements a vTPM. There is a one to one mapping between running vtpm-stubdom instances and logical vtpms on the system. The vTPM Platform Configuration Registers (PCRs) are normally all initialized to zero.”h]”hŒêA mini-os stub domain that implements a vTPM. There is a one to one mapping between running vtpm-stubdom instances and logical vtpms on the system. The vTPM Platform Configuration Registers (PCRs) are normally all initialized to zero.”…””}”(hj,hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KThj)ubah}”(h]”h ]”h"]”h$]”h&]”uh1jahjubeh}”(h]”h ]”h"]”h$]”h&]”uh1jKhŸh¶h KWhjubah}”(h]”h ]”h"]”h$]”h&]”uh1jFhjubah}”(h]”h ]”h"]”h$]”h&]”uh1j@hj=hžhhŸNh NubjA)”}”(hX0mini-os/tpmfront: Mini-os TPM frontend driver. The vTPM mini-os domain vtpm-stubdom uses this driver to communicate with vtpmmgr-stubdom. This driver is also used in mini-os domains such as pv-grub that talk to the vTPM domain. ”h]”jG)”}”(hhh]”jL)”}”(hŒämini-os/tpmfront: Mini-os TPM frontend driver. The vTPM mini-os domain vtpm-stubdom uses this driver to communicate with vtpmmgr-stubdom. This driver is also used in mini-os domains such as pv-grub that talk to the vTPM domain. ”h]”(jR)”}”(hŒmini-os/tpmfront:”h]”hŒmini-os/tpmfront:”…””}”(hj]hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jQhŸh¶h K]hjYubjb)”}”(hhh]”h¸)”}”(hŒÑMini-os TPM frontend driver. The vTPM mini-os domain vtpm-stubdom uses this driver to communicate with vtpmmgr-stubdom. This driver is also used in mini-os domains such as pv-grub that talk to the vTPM domain.”h]”hŒÑMini-os TPM frontend driver. The vTPM mini-os domain vtpm-stubdom uses this driver to communicate with vtpmmgr-stubdom. This driver is also used in mini-os domains such as pv-grub that talk to the vTPM domain.”…””}”(hjnhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KZhjkubah}”(h]”h ]”h"]”h$]”h&]”uh1jahjYubeh}”(h]”h ]”h"]”h$]”h&]”uh1jKhŸh¶h K]hjVubah}”(h]”h ]”h"]”h$]”h&]”uh1jFhjRubah}”(h]”h ]”h"]”h$]”h&]”uh1j@hj=hžhhŸNh NubjA)”}”(hXpvtpmmgr-stubdom: A mini-os domain that implements the vTPM manager. There is only one vTPM manager and it should be running during the entire lifetime of the machine. This domain regulates access to the physical TPM on the system and secures the persistent state of each vTPM. ”h]”jG)”}”(hhh]”jL)”}”(hXvtpmmgr-stubdom: A mini-os domain that implements the vTPM manager. There is only one vTPM manager and it should be running during the entire lifetime of the machine. This domain regulates access to the physical TPM on the system and secures the persistent state of each vTPM. ”h]”(jR)”}”(hŒvtpmmgr-stubdom:”h]”hŒvtpmmgr-stubdom:”…””}”(hjŸhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jQhŸh¶h Kdhj›ubjb)”}”(hhh]”h¸)”}”(hXA mini-os domain that implements the vTPM manager. There is only one vTPM manager and it should be running during the entire lifetime of the machine. This domain regulates access to the physical TPM on the system and secures the persistent state of each vTPM.”h]”hXA mini-os domain that implements the vTPM manager. There is only one vTPM manager and it should be running during the entire lifetime of the machine. This domain regulates access to the physical TPM on the system and secures the persistent state of each vTPM.”…””}”(hj°hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K`hj­ubah}”(h]”h ]”h"]”h$]”h&]”uh1jahj›ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jKhŸh¶h Kdhj˜ubah}”(h]”h ]”h"]”h$]”h&]”uh1jFhj”ubah}”(h]”h ]”h"]”h$]”h&]”uh1j@hj=hžhhŸNh NubjA)”}”(hX9mini-os/tpm_tis: Mini-os TPM version 1.2 TPM Interface Specification (TIS) driver. This driver used by vtpmmgr-stubdom to talk directly to the hardware TPM. Communication is facilitated by mapping hardware memory pages into vtpmmgr-stubdom. ”h]”jG)”}”(hhh]”jL)”}”(hŒñmini-os/tpm_tis: Mini-os TPM version 1.2 TPM Interface Specification (TIS) driver. This driver used by vtpmmgr-stubdom to talk directly to the hardware TPM. Communication is facilitated by mapping hardware memory pages into vtpmmgr-stubdom. ”h]”(jR)”}”(hŒmini-os/tpm_tis:”h]”hŒmini-os/tpm_tis:”…””}”(hjáhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jQhŸh¶h KjhjÝubjb)”}”(hhh]”h¸)”}”(hŒßMini-os TPM version 1.2 TPM Interface Specification (TIS) driver. This driver used by vtpmmgr-stubdom to talk directly to the hardware TPM. Communication is facilitated by mapping hardware memory pages into vtpmmgr-stubdom.”h]”hŒßMini-os TPM version 1.2 TPM Interface Specification (TIS) driver. This driver used by vtpmmgr-stubdom to talk directly to the hardware TPM. Communication is facilitated by mapping hardware memory pages into vtpmmgr-stubdom.”…””}”(hjòhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kghjïubah}”(h]”h ]”h"]”h$]”h&]”uh1jahjÝubeh}”(h]”h ]”h"]”h$]”h&]”uh1jKhŸh¶h KjhjÚubah}”(h]”h ]”h"]”h$]”h&]”uh1jFhjÖubah}”(h]”h ]”h"]”h$]”h&]”uh1j@hj=hžhhŸNh NubjA)”}”(hŒUHardware TPM: The physical TPM that is soldered onto the motherboard. ”h]”jG)”}”(hhh]”jL)”}”(hŒGHardware TPM: The physical TPM that is soldered onto the motherboard. ”h]”(jR)”}”(hŒ Hardware TPM:”h]”hŒ Hardware TPM:”…””}”(hj#hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jQhŸh¶h Knhjubjb)”}”(hhh]”h¸)”}”(hŒ7The physical TPM that is soldered onto the motherboard.”h]”hŒ7The physical TPM that is soldered onto the motherboard.”…””}”(hj4hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kmhj1ubah}”(h]”h ]”h"]”h$]”h&]”uh1jahjubeh}”(h]”h ]”h"]”h$]”h&]”uh1jKhŸh¶h Knhjubah}”(h]”h ]”h"]”h$]”h&]”uh1jFhjubah}”(h]”h ]”h"]”h$]”h&]”uh1j@hj=hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ*”uh1j;hŸh¶h KEhj hžhubeh}”(h]”Œdesign-overview”ah ]”h"]”Œdesign overview”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Kubh¢)”}”(hhh]”(h§)”}”(hŒIntegration With Xen”h]”hŒIntegration With Xen”…””}”(hjmhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjjhžhhŸh¶h Kqubh¸)”}”(hXSSupport for the vTPM driver was added in Xen using the libxl toolstack in Xen 4.3. See the Xen documentation (docs/misc/vtpm.txt) for details on setting up the vTPM and vTPM Manager stub domains. Once the stub domains are running, a vTPM device is set up in the same manner as a disk or network device in the domain's configuration file.”h]”hXUSupport for the vTPM driver was added in Xen using the libxl toolstack in Xen 4.3. See the Xen documentation (docs/misc/vtpm.txt) for details on setting up the vTPM and vTPM Manager stub domains. Once the stub domains are running, a vTPM device is set up in the same manner as a disk or network device in the domain’s configuration file.”…””}”(hj{hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kshjjhžhubh¸)”}”(hŒõIn order to use features such as IMA that require a TPM to be loaded prior to the initrd, the xen-tpmfront driver must be compiled in to the kernel. If not using such features, the driver can be compiled as a module and will be loaded as usual.”h]”hŒõIn order to use features such as IMA that require a TPM to be loaded prior to the initrd, the xen-tpmfront driver must be compiled in to the kernel. If not using such features, the driver can be compiled as a module and will be loaded as usual.”…””}”(hj‰hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kyhjjhžhubeh}”(h]”Œintegration-with-xen”ah ]”h"]”Œintegration with xen”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Kqubeh}”(h]”Œvirtual-tpm-interface-for-xen”ah ]”h"]”Œvirtual tpm interface for xen”ah$]”h&]”uh1h¡hhhžhhŸh¶h Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”h¶uh1hŒcurrent_source”NŒ current_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(h¦NŒ generator”NŒ datestamp”NŒ source_link”NŒ source_url”NŒ toc_backlinks”Œentry”Œfootnote_backlinks”KŒ sectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒ strip_classes”NŒ report_level”KŒ halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ traceback”ˆŒinput_encoding”Œ utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”jÊŒerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œ language_code”Œen”Œrecord_dependencies”NŒconfig”NŒ id_prefix”hŒauto_id_prefix”Œid”Œ dump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”h¶Œ _destination”NŒ _config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒ raw_enabled”KŒline_length_limit”M'Œpep_references”NŒ pep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒ rfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œ smart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œ docinfo_xform”KŒsectsubtitle_xform”‰Œ image_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”(j¤j¡jjjgjdjœj™uŒ nametypes”}”(j¤‰j‰jg‰jœ‰uh}”(j¡h£jhÕjdj j™jjuŒ footnote_refs”}”Œ citation_refs”}”Œ autofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ footnotes”]”Œ citations”]”Œautofootnote_start”KŒsymbol_footnote_start”KŒ id_counter”Œ collections”ŒCounter”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”Œ transformer”NŒ include_log”]”Œ decoration”Nhžhub.