€•[Œ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”Œ \ [<#opt_params> ]”h]”hŒP \ [<#opt_params> ]”…””}”hj sbah}”(h]”h ]”h"]”h$]”h&]”Œ xml:space”Œpreserve”uh1jh³hÊh´K hh·h²hubhŒdefinition_list”“”)”}”(hhh]”(hŒdefinition_list_item”“”)”}”(hX, Encryption cipher type. The cipher specifications format is:: cipher Examples:: aes-xts-plain64 The cipher type corresponds to the encryption modes supported by inline crypto in the block layer. Currently, only BLK_ENCRYPTION_MODE_AES_256_XTS (i.e. aes-xts-plain64) is supported. ”h]”(hŒterm”“”)”}”(hŒ”h]”hŒ”…””}”(hj'h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j%h³hÊh´Khj!ubhŒ definition”“”)”}”(hhh]”(hÌ)”}”(hŒEncryption cipher type.”h]”hŒEncryption cipher type.”…””}”(hj:h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Khj7ubhÌ)”}”(hŒ%The cipher specifications format is::”h]”hŒ$The cipher specifications format is:”…””}”(hjHh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Khj7ubj )”}”(hŒcipher”h]”hŒcipher”…””}”hjVsbah}”(h]”h ]”h"]”h$]”h&]”jjuh1jh³hÊh´Khj7ubhÌ)”}”(hŒ Examples::”h]”hŒ Examples:”…””}”(hjdh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Khj7ubj )”}”(hŒaes-xts-plain64”h]”hŒaes-xts-plain64”…””}”hjrsbah}”(h]”h ]”h"]”h$]”h&]”jjuh1jh³hÊh´Khj7ubhÌ)”}”(hŒ·The cipher type corresponds to the encryption modes supported by inline crypto in the block layer. Currently, only BLK_ENCRYPTION_MODE_AES_256_XTS (i.e. aes-xts-plain64) is supported.”h]”hŒ·The cipher type corresponds to the encryption modes supported by inline crypto in the block layer. Currently, only BLK_ENCRYPTION_MODE_AES_256_XTS (i.e. aes-xts-plain64) is supported.”…””}”(hj€h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Khj7ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j5hj!ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jh³hÊh´Khjubj )”}”(hXŽ Key used for encryption. It is encoded either as a hexadecimal number or it can be passed as prefixed with single colon character (':') for keys residing in kernel keyring service. You can only use key sizes that are valid for the selected cipher. Note that the size in bytes of a valid key must be in bellow range. [BLK_CRYPTO_KEY_TYPE_RAW, BLK_CRYPTO_KEY_TYPE_HW_WRAPPED] ”h]”(j&)”}”(hŒ”h]”hŒ”…””}”(hjžh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j%h³hÊh´K&hjšubj6)”}”(hhh]”(hÌ)”}”(hXHKey used for encryption. It is encoded either as a hexadecimal number or it can be passed as prefixed with single colon character (':') for keys residing in kernel keyring service. You can only use key sizes that are valid for the selected cipher. Note that the size in bytes of a valid key must be in bellow range.”h]”hXLKey used for encryption. It is encoded either as a hexadecimal number or it can be passed as prefixed with single colon character (‘:’) for keys residing in kernel keyring service. You can only use key sizes that are valid for the selected cipher. Note that the size in bytes of a valid key must be in bellow range.”…””}”(hj¯h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K hj¬ubhŒ block_quote”“”)”}”(hŒ:[BLK_CRYPTO_KEY_TYPE_RAW, BLK_CRYPTO_KEY_TYPE_HW_WRAPPED] ”h]”hÌ)”}”(hŒ9[BLK_CRYPTO_KEY_TYPE_RAW, BLK_CRYPTO_KEY_TYPE_HW_WRAPPED]”h]”hŒ9[BLK_CRYPTO_KEY_TYPE_RAW, BLK_CRYPTO_KEY_TYPE_HW_WRAPPED]”…””}”(hjÃh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K&hj¿ubah}”(h]”h ]”h"]”h$]”h&]”uh1j½h³hÊh´K&hj¬ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j5hjšubeh}”(h]”h ]”h"]”h$]”h&]”uh1jh³hÊh´K&hjh²hubj )”}”(hŒ~ The kernel keyring key is identified by string in following format: ::. ”h]”(j&)”}”(hŒ ”h]”hŒ ”…””}”(hjçh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j%h³hÊh´K*hjãubj6)”}”(hhh]”hÌ)”}”(hŒpThe kernel keyring key is identified by string in following format: ::.”h]”hŒpThe kernel keyring key is identified by string in following format: ::.”…””}”(hjøh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K)hjõubah}”(h]”h ]”h"]”h$]”h&]”uh1j5hjãubeh}”(h]”h ]”h"]”h$]”h&]”uh1jh³hÊh´K*hjh²hubj )”}”(hŒt The encryption key size in bytes. The kernel key payload size must match the value passed in . ”h]”(j&)”}”(hŒ ”h]”hŒ ”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j%h³hÊh´K.hjubj6)”}”(hhh]”hÌ)”}”(hŒhThe encryption key size in bytes. The kernel key payload size must match the value passed in .”h]”hŒhThe encryption key size in bytes. The kernel key payload size must match the value passed in .”…””}”(hj'h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K-hj$ubah}”(h]”h ]”h"]”h$]”h&]”uh1j5hjubeh}”(h]”h ]”h"]”h$]”h&]”uh1jh³hÊh´K.hjh²hubj )”}”(hŒv The type of the key inside the kernel keyring. It can be either 'logon', or 'trusted' kernel key type. ”h]”(j&)”}”(hŒ”h]”hŒ”…””}”(hjEh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j%h³hÊh´K2hjAubj6)”}”(hhh]”hÌ)”}”(hŒfThe type of the key inside the kernel keyring. It can be either 'logon', or 'trusted' kernel key type.”h]”hŒnThe type of the key inside the kernel keyring. It can be either ‘logon’, or ‘trusted’ kernel key type.”…””}”(hjVh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K1hjSubah}”(h]”h ]”h"]”h$]”h&]”uh1j5hjAubeh}”(h]”h ]”h"]”h$]”h&]”uh1jh³hÊh´K2hjh²hubj )”}”(hŒ| The kernel keyring key description inlinecrypt target should look for when loading key of . ”h]”(j&)”}”(hŒ”h]”hŒ”…””}”(hjth²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j%h³hÊh´K6hjpubj6)”}”(hhh]”hÌ)”}”(hŒiThe kernel keyring key description inlinecrypt target should look for when loading key of .”h]”hŒiThe kernel keyring key description inlinecrypt target should look for when loading key of .”…””}”(hj…h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K5hj‚ubah}”(h]”h ]”h"]”h$]”h&]”uh1j5hjpubeh}”(h]”h ]”h"]”h$]”h&]”uh1jh³hÊh´K6hjh²hubj )”}”(hŒg The IV offset is a sector count that is added to the sector number before creating the IV. ”h]”(j&)”}”(hŒ ”h]”hŒ ”…””}”(hj£h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j%h³hÊh´K:hjŸubj6)”}”(hhh]”hÌ)”}”(hŒZThe IV offset is a sector count that is added to the sector number before creating the IV.”h]”hŒZThe IV offset is a sector count that is added to the sector number before creating the IV.”…””}”(hj´h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K9hj±ubah}”(h]”h ]”h"]”h$]”h&]”uh1j5hjŸubeh}”(h]”h ]”h"]”h$]”h&]”uh1jh³hÊh´K:hjh²hubj )”}”(hŒ¶ This is the device that is going to be used as backend and contains the encrypted data. You can specify it as a path like /dev/xxx or a device number :. ”h]”(j&)”}”(hŒ ”h]”hŒ ”…””}”(hjÒh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j%h³hÊh´K?hjÎubj6)”}”(hhh]”hÌ)”}”(hŒ§This is the device that is going to be used as backend and contains the encrypted data. You can specify it as a path like /dev/xxx or a device number :.”h]”hŒ§This is the device that is going to be used as backend and contains the encrypted data. You can specify it as a path like /dev/xxx or a device number :.”…””}”(hjãh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K=hjàubah}”(h]”h ]”h"]”h$]”h&]”uh1j5hjÎubeh}”(h]”h ]”h"]”h$]”h&]”uh1jh³hÊh´K?hjh²hubj )”}”(hŒL Starting sector within the device where the encrypted data begins. ”h]”(j&)”}”(hŒ”h]”hŒ”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j%h³hÊh´KBhjýubj6)”}”(hhh]”hÌ)”}”(hŒBStarting sector within the device where the encrypted data begins.”h]”hŒBStarting sector within the device where the encrypted data begins.”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KBhjubah}”(h]”h ]”h"]”h$]”h&]”uh1j5hjýubeh}”(h]”h ]”h"]”h$]”h&]”uh1jh³hÊh´KBhjh²hubj )”}”(hXC<#opt_params> Number of optional parameters. If there are no optional parameters, the optional parameters section can be skipped or #opt_params can be zero. Otherwise #opt_params is the number of following arguments. Example of optional parameters section: keytype:raw allow_discards sector_size:4096 iv_large_sectors ”h]”(j&)”}”(hŒ <#opt_params>”h]”hŒ <#opt_params>”…””}”(hj0h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j%h³hÊh´KJhj,ubj6)”}”(hhh]”(hÌ)”}”(hŒÊNumber of optional parameters. If there are no optional parameters, the optional parameters section can be skipped or #opt_params can be zero. Otherwise #opt_params is the number of following arguments.”h]”hŒÊNumber of optional parameters. If there are no optional parameters, the optional parameters section can be skipped or #opt_params can be zero. Otherwise #opt_params is the number of following arguments.”…””}”(hjAh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KEhj>ubj)”}”(hhh]”j )”}”(hŒeExample of optional parameters section: keytype:raw allow_discards sector_size:4096 iv_large_sectors ”h]”(j&)”}”(hŒ'Example of optional parameters section:”h]”hŒ'Example of optional parameters section:”…””}”(hjVh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j%h³hÊh´KJhjRubj6)”}”(hhh]”hÌ)”}”(hŒubeh}”(h]”h ]”h"]”h$]”h&]”uh1j5hj,ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jh³hÊh´KJhjh²hubj )”}”(hŒ® The type of the key as seen by the block layer, either standard or hardware-wrapped. The string is supplied in the table as or . ”h]”(j&)”}”(hŒ ”h]”hŒ ”…””}”(hj—h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j%h³hÊh´KOhj“ubj6)”}”(hhh]”hÌ)”}”(hŒ¢The type of the key as seen by the block layer, either standard or hardware-wrapped. The string is supplied in the table as or .”h]”hŒ¢The type of the key as seen by the block layer, either standard or hardware-wrapped. The string is supplied in the table as or .”…””}”(hj¨h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KMhj¥ubah}”(h]”h ]”h"]”h$]”h&]”uh1j5hj“ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jh³hÊh´KOhjh²hubj )”}”(hX¹allow_discards Block discard requests (a.k.a. TRIM) are passed through the inlinecrypt device. The default is to ignore discard requests. WARNING: Assess the specific security risks carefully before enabling this option. For example, allowing discards on encrypted devices may lead to the leak of information about the ciphertext device (filesystem type, used space etc.) if the discarded blocks can be located easily on the device later. ”h]”(j&)”}”(hŒallow_discards”h]”hŒallow_discards”…””}”(hjÆh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j%h³hÊh´KYhjÂubj6)”}”(hhh]”(hÌ)”}”(hŒzBlock discard requests (a.k.a. TRIM) are passed through the inlinecrypt device. The default is to ignore discard requests.”h]”hŒzBlock discard requests (a.k.a. TRIM) are passed through the inlinecrypt device. The default is to ignore discard requests.”…””}”(hj×h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KRhjÔubhÌ)”}”(hX-WARNING: Assess the specific security risks carefully before enabling this option. For example, allowing discards on encrypted devices may lead to the leak of information about the ciphertext device (filesystem type, used space etc.) if the discarded blocks can be located easily on the device later.”h]”hX-WARNING: Assess the specific security risks carefully before enabling this option. For example, allowing discards on encrypted devices may lead to the leak of information about the ciphertext device (filesystem type, used space etc.) if the discarded blocks can be located easily on the device later.”…””}”(hjåh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KUhjÔubeh}”(h]”h ]”h"]”h$]”h&]”uh1j5hjÂubeh}”(h]”h ]”h"]”h$]”h&]”uh1jh³hÊh´KYhjh²hubj )”}”(hŒçsector_size: Use as the encryption unit instead of 512 bytes sectors. This option can be in range 512 - 4096 bytes and must be power of two. Virtual device will announce this size as a minimal IO and logical sector. ”h]”(j&)”}”(hŒsector_size:”h]”hŒsector_size:”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j%h³hÊh´K^hjÿubj6)”}”(hhh]”hÌ)”}”(hŒÒUse as the encryption unit instead of 512 bytes sectors. This option can be in range 512 - 4096 bytes and must be power of two. Virtual device will announce this size as a minimal IO and logical sector.”h]”hŒÒUse as the encryption unit instead of 512 bytes sectors. This option can be in range 512 - 4096 bytes and must be power of two. Virtual device will announce this size as a minimal IO and logical sector.”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K\hjubah}”(h]”h ]”h"]”h$]”h&]”uh1j5hjÿubeh}”(h]”h ]”h"]”h$]”h&]”uh1jh³hÊh´K^hjh²hubj )”}”(hX£iv_large_sectors Use -based sector numbers for IV generation instead of 512-byte sectors. For dm-inlinecrypt, this flag must be specified when is larger than 512 bytes. The legacy 512-byte-based IV behavior is not supported. When specified, if is 4096 bytes, plain64 IV for the second sector will be 1, and must be a multiple of (in 512-byte units). ”h]”(j&)”}”(hŒiv_large_sectors”h]”hŒiv_large_sectors”…””}”(hj2h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j%h³hÊh´Kjhj.ubj6)”}”(hhh]”(hÌ)”}”(hŒUUse -based sector numbers for IV generation instead of 512-byte sectors.”h]”hŒUUse -based sector numbers for IV generation instead of 512-byte sectors.”…””}”(hjCh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Kahj@ubhÌ)”}”(hŒ”For dm-inlinecrypt, this flag must be specified when is larger than 512 bytes. The legacy 512-byte-based IV behavior is not supported.”h]”hŒ”For dm-inlinecrypt, this flag must be specified when is larger than 512 bytes. The legacy 512-byte-based IV behavior is not supported.”…””}”(hjQh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Kdhj@ubhÌ)”}”(hŒ¤When specified, if is 4096 bytes, plain64 IV for the second sector will be 1, and must be a multiple of (in 512-byte units).”h]”hŒ¤When specified, if is 4096 bytes, plain64 IV for the second sector will be 1, and must be a multiple of (in 512-byte units).”…””}”(hj_h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Khhj@ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j5hj.ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jh³hÊh´Kjhjh²hubeh}”(h]”h ]”h"]”h$]”h&]”uh1jhh·h²hh³hÊh´Nubh¶)”}”(hhh]”(h»)”}”(hŒExample scripts”h]”hŒExample scripts”…””}”(hj‚h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjh²hh³hÊh´KmubhÌ)”}”(hXCurrently, dm-inlinecrypt devices must be set up directly using dmsetup. There is no userspace support yet to integrate dm-inlinecrypt with LUKS or cryptsetup. In particular, cryptsetup currently only supports dm-crypt, and cannot be used to create dm-inlinecrypt mappings.”h]”hXCurrently, dm-inlinecrypt devices must be set up directly using dmsetup. There is no userspace support yet to integrate dm-inlinecrypt with LUKS or cryptsetup. In particular, cryptsetup currently only supports dm-crypt, and cannot be used to create dm-inlinecrypt mappings.”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Knhjh²hubhÌ)”}”(hŒUThe following examples demonstrate how to create dm-inlinecrypt devices using dmsetup”h]”hŒUThe following examples demonstrate how to create dm-inlinecrypt devices using dmsetup”…””}”(hjžh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Kshjh²hubj )”}”(hŒç#!/bin/sh # Create a inlinecrypt device using dmsetup dmsetup create inlinecrypt1 --table "0 `blockdev --getsz $1` inlinecrypt aes-xts-plain64 babebabebabebabebabebabebabebabebabebabebabebabebabebabebabebabe 0 0 $1 0 1 keytype:raw"”h]”hŒç#!/bin/sh # Create a inlinecrypt device using dmsetup dmsetup create inlinecrypt1 --table "0 `blockdev --getsz $1` inlinecrypt aes-xts-plain64 babebabebabebabebabebabebabebabebabebabebabebabebabebabebabebabe 0 0 $1 0 1 keytype:raw"”…””}”hj¬sbah}”(h]”h ]”h"]”h$]”h&]”jjuh1jh³hÊh´Kxhjh²hubj )”}”(hŒü#!/bin/sh # Create a inlinecrypt device using dmsetup when encryption key is stored in keyring service dmsetup create inlinecrypt2 --table "0 `blockdev --getsz $1` inlinecrypt aes-xts-plain64 :64:logon:fde:dminlinecrypt_test_key 0 0 $1 0 1 keytype:raw"”h]”hŒü#!/bin/sh # Create a inlinecrypt device using dmsetup when encryption key is stored in keyring service dmsetup create inlinecrypt2 --table "0 `blockdev --getsz $1` inlinecrypt aes-xts-plain64 :64:logon:fde:dminlinecrypt_test_key 0 0 $1 0 1 keytype:raw"”…””}”hjºsbah}”(h]”h ]”h"]”h$]”h&]”jjuh1jh³hÊh´K~hjh²hubeh}”(h]”Œexample-scripts”ah ]”h"]”Œexample scripts”ah$]”h&]”uh1hµhh·h²hh³hÊh´Kmubeh}”(h]”Œdm-inlinecrypt”ah ]”h"]”Œdm-inlinecrypt”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ÒjÍjÊuŒ nametypes”}”(jÕ‰j͉uh}”(jÒh·jÊjuŒ 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.