jzRddlZddlZddlZddlmZmZddlmZmZm Z m Z ddl m Z m Z mZmZmZmZmZmZmZmZddlmZddlmZmZmZmZmZmZmZm Z m!Z!Gdd Z"d Z#d e$d e$fd Z%GddZ&GddZ'GddeZ(Gdde)eZ*GddZ+GddZ,y)N)EnumIntEnum)AnyOptionalUnioncast) CryptAES CryptBase CryptIdentityCryptRC4aes_cbc_decryptaes_cbc_encryptaes_ecb_decryptaes_ecb_encrypt rc4_decrypt rc4_encrypt)logger_warning) ArrayObjectByteStringObjectDictionaryObject NameObject NumberObject PdfObject StreamObjectTextStringObjectcreate_string_objectcDeZdZdedededdfdZdedefdZdedefd Zy) CryptFilter stm_crypt str_cryptef_cryptreturnNc.||_||_||_yN)r r!r")selfr r!r"s [/var/www/html/Fitness-lenito-AI-main/venv/lib/python3.12/site-packages/pypdf/_encryption.py__init__zCryptFilter.__init__=s #"  objct|tr2jj|j}t|}|St|t r6jj|j }t|}|St|trt}|j||jjj|j|jD]\}}j|||<|}|St|tr:t}|jD]\}}j|||<|}|St|trtfd|D}|S)Nc3@K|]}j|ywr%)encrypt_object).0xr&s r' z-CryptFilter.encrypt_object..[sBcd11!4cs) isinstancerr!encryptoriginal_bytesrget_encoded_bytesrupdateset_datar _dataitemsr-rr)r&r*dataobj2keyvalues` r'r-zCryptFilter.encrypt_objectGsP c+ ,>>))#*<*<=D"4(C$ #- .>>))#*?*?*ABD"4(C \ *>D KK  MM$..00; <!iik U //6S *C - .#%D!iik U //6S *C [ )BcBBC r)cbt|ttfr2|jj |j }t |}|St|trX|jj |j|_ |jD]\}}|j|||<|St|tr.|jD]\}}|j|||<|St|tr0tt|D]}|j||||<|Sr%)r1rrr!decryptr3rrr r7r8decrypt_objectrrrangelen)r&r*r9r;r<is r'r?zCryptFilter.decrypt_object^s  c,.>? @>>))#*<*<=D&t,C \ *..syy9CI!iik U..u5C* - .!iik U..u5C*  [ )3s8_,,SV4A% r))__name__ __module__ __qualname__r r(rr-r?r)r'rr<sS!!! !  !) .) r)rs (N^NuAdNV..h>/ dSizr9r#c|tzddS)N )_PADDING)r9s r'_paddingrJus 8OSb !!r)ceZdZededededededededefd Zed edededefd Zed ed ededefdZ ededededefdZ ed ededededededededefdZ ed ededededededededefdZ y)AlgV4passwordrevkey_sizeo_entryP id1_entrymetadata_encryptedr#ct|}tj|}|j||jt j d||j||dk\r|s|jd|j } |dz} |dk\r6tdD](} tj| d| j } *| d| S)u Algorithm 2: Computing an encryption key. a) Pad or truncate the password string to exactly 32 bytes. If the password string is more than 32 bytes long, use only its first 32 bytes; if it is less than 32 bytes long, pad it by appending the required number of additional bytes from the beginning of the following padding string: < 28 BF 4E 5E 4E 75 8A 41 64 00 4E 56 FF FA 01 08 2E 2E 00 B6 D0 68 3E 80 2F 0C A9 FE 64 53 69 7A > That is, if the password string is n bytes long, append the first 32 - n bytes of the padding string to the end of the password string. If the password string is empty (zero-length), meaning there is no user password, substitute the entire padding string in its place. b) Initialize the MD5 hash function and pass the result of step (a) as input to this function. c) Pass the value of the encryption dictionary’s O entry to the MD5 hash function. ("Algorithm 3: Computing the encryption dictionary’s O (owner password) value" shows how the O value is computed.) d) Convert the integer value of the P entry to a 32-bit unsigned binary number and pass these bytes to the MD5 hash function, low-order byte first. e) Pass the first element of the file’s file identifier array (the value of the ID entry in the document’s trailer dictionary; see Table 15) to the MD5 hash function. f) (Security handlers of revision 4 or greater) If document metadata is not being encrypted, pass 4 bytes with the value 0xFFFFFFFF to the MD5 hash function. g) Finish the hash. h) (Security handlers of revision 3 or greater) Do the following 50 times: Take the output from the previous MD5 hash and pass the first n bytes of the output as input into a new MD5 hash, where n is the number of bytes of the encryption key as defined by the value of the encryption dictionary’s Length entry. i) Set the encryption key to the first n bytes of the output from the final MD5 hash, where n shall always be 5 for security handlers of revision 2 but, for security handlers of revision 3 or greater, shall depend on the value of the encryption dictionary’s Length entry. Args: password: The encryption secret as a bytes-string rev: The encryption revision (see PDF standard) key_size: The size of the key in bytes o_entry: The owner entry P: A set of flags specifying which operations shall be permitted when the document is opened with user access. If bit 2 is set to 1, all other bits are ignored and all operations are permitted. If bit 2 is set to 0, permission for operations are based on the values of the remaining flags defined in Table 24. id1_entry: metadata_encrypted: A boolean indicating if the metadata is encrypted. Returns: The u_hash digest of length key_size .37aAE7)rJrr@bytes)rjrkrNr`rc4_encr;rBs @r'compute_O_valuezAlgV4.compute_O_valuesU ] #gq) !81b\3733%c73"r)r;c0|dkrt|tS tjt}|j |t||j }t ddD]"tfd|D}t||}$t|S)u Algorithm 4: Computing the encryption dictionary’s U (user password) value. (Security handlers of revision 2) a) Create an encryption key based on the user password string, as described in "Algorithm 2: Computing an encryption key". b) Encrypt the 32-byte padding string shown in step (a) of "Algorithm 2: Computing an encryption key", using an RC4 encryption function with the encryption key from the preceding step. c) Store the result of step (b) as the value of the U entry in the encryption dictionary. Args: key: rev: The encryption revision (see PDF standard) id1_entry: Returns: The value rrmc3(K|] }|z  ywr%rFros r'r0z(AlgV4.compute_U_value..Ps/3aAE3rq) rrIr[r\r5r_r@rrrJ)r;rNrRrarsrjrBs @r'compute_U_valuezAlgV4.compute_U_values0 !8sH- - 2X& i c6==?3q"A/3//G!'73G  r)u_entryc tj|||||||}tj|||} |dk\r | dd} |dd}| |k7rd}|S)ur Algorithm 6: Authenticating the user password. a) Perform all but the last step of "Algorithm 4: Computing the encryption dictionary’s U (user password) value (Security handlers of revision 2)" or "Algorithm 5: Computing the encryption dictionary’s U (user password) value (Security handlers of revision 3 or greater)" using the supplied password string. b) If the result of step (a) is equal to the value of the encryption dictionary’s U entry (comparing on the first 16 bytes in the case of security handlers of revision 3 or greater), the password supplied is the correct user password. The key obtained in step (a) (that is, in the first step of "Algorithm 4: Computing the encryption dictionary’s U (user password) value (Security handlers of revision 2)" or "Algorithm 5: Computing the encryption dictionary’s U (user password) value (Security handlers of revision 3 or greater)") shall be used to decrypt the document. Args: user_password: The user password as a bytes stream rev: The encryption revision (see PDF standard) key_size: The size of the key in bytes o_entry: The owner entry u_entry: The user entry P: A set of flags specifying which operations shall be permitted when the document is opened with user access. If bit 2 is set to 1, all other bits are ignored and all operations are permitted. If bit 2 is set to 0, permission for operations are based on the values of the remaining flags defined in Table 24. id1_entry: metadata_encrypted: A boolean indicating if the metadata is encrypted. Returns: The key rYNr))rLrerx) rkrNrOrPryrQrRrSr;u_values r'verify_user_passwordzAlgV4.verify_user_passwordTsj` 3'1iAS ''S)< !8crlGcrlG g C r)c  tj|||}|dkr t||} n4|} tdddD]" t fd|D} t| | } $tj | |||||||S)uN Algorithm 7: Authenticating the owner password. a) Compute an encryption key from the supplied password string, as described in steps (a) to (d) of "Algorithm 3: Computing the encryption dictionary’s O (owner password) value". b) (Security handlers of revision 2 only) Decrypt the value of the encryption dictionary’s O entry, using an RC4 encryption function with the encryption key computed in step (a). (Security handlers of revision 3 or greater) Do the following 20 times: Decrypt the value of the encryption dictionary’s O entry (first iteration) or the output from the previous iteration (all subsequent iterations), using an RC4 encryption function with a different encryption key at each iteration. The key shall be generated by taking the original key (obtained in step (a)) and performing an XOR (exclusive or) operation between each byte of the key and the single-byte value of the iteration counter (from 19 to 0). c) The result of step (b) purports to be the user password. Authenticate this user password using "Algorithm 6: Authenticating the user password". If it is correct, the password supplied is the correct owner password. Args: owner_password: rev: The encryption revision (see PDF standard) key_size: The size of the key in bytes o_entry: The owner entry u_entry: The user entry P: A set of flags specifying which operations shall be permitted when the document is opened with user access. If bit 2 is set to 1, all other bits are ignored and all operations are permitted. If bit 2 is set to 0, permission for operations are based on the values of the remaining flags defined in Table 24. id1_entry: metadata_encrypted: A boolean indicating if the metadata is encrypted. Returns: bytes rvc3(K|] }|z  ywr%rFros r'r0z.AlgV4.verify_owner_password..rprq)rLrirr@rrr}) rfrNrOrPryrQrRrSrjrkr;rBs @r'verify_owner_passwordzAlgV4.verify_owner_passwordsh++NCJ !8'9M#M2r2&3733 +C ? '))         r)N) rCrDrE staticmethodrrintboolrerirtrxr}rrFr)r'rLrLysR&R& R&R& R&  R&  R&!R& R&R&h0.E0.0.s0.u0.0.du35*9!U9!9!9!59!9!v88 88 8  8  88!8 88tE E E E  E  E  E E !E  E E r)rLc^eZdZededededededef dZedededededef d Zededed ed edef d Zed ededede de f dZ edededed edede de e e ffdZ ededed edeeeffdZededed ededeeeff dZed edede defdZy)AlgV5RrMo_valueoe_valuer|r#c|dd}tj|||dd|dd|ddk7rytdtdD}tj|||dd|dd}t |||S) u Algorithm 3.2a Computing an encryption key. To understand the algorithm below, it is necessary to treat the O and U strings in the Encrypt dictionary as made up of three sections. The first 32 bytes are a hash value (explained below). The next 8 bytes are called the Validation Salt. The final 8 bytes are called the Key Salt. 1. The password string is generated from Unicode input by processing the input string with the SASLprep (IETF RFC 4013) profile of stringprep (IETF RFC 3454), and then converting to a UTF-8 representation. 2. Truncate the UTF-8 representation to 127 bytes if it is longer than 127 bytes. 3. Test the password against the owner key by computing the SHA-256 hash of the UTF-8 password concatenated with the 8 bytes of owner Validation Salt, concatenated with the 48-byte U string. If the 32-byte result matches the first 32 bytes of the O string, this is the owner password. Compute an intermediate owner key by computing the SHA-256 hash of the UTF-8 password concatenated with the 8 bytes of owner Key Salt, concatenated with the 48-byte U string. The 32-byte result is the key used to decrypt the 32-byte OE string using AES-256 in CBC mode with no padding and an initialization vector of zero. The 32-byte result is the file encryption key. 4. Test the password against the user key by computing the SHA-256 hash of the UTF-8 password concatenated with the 8 bytes of user Validation Salt. If the 32 byte result matches the first 32 bytes of the U string, this is the user password. Compute an intermediate user key by computing the SHA-256 hash of the UTF-8 password concatenated with the 8 bytes of user Key Salt. The 32-byte result is the key used to decrypt the 32-byte UE string using AES-256 in CBC mode with no padding and an initialization vector of zero. The 32-byte result is the file encryption key. 5. Decrypt the 16-byte Perms string using AES-256 in ECB mode with an initialization vector of zero and the file encryption key as the key. Verify that bytes 9-11 of the result are the characters ‘a’, ‘d’, ‘b’. Bytes 0-3 of the decrypted Perms entry, treated as a little-endian integer, are the user permissions. They should match the value in the P key. Args: R: A number specifying which revision of the standard security handler shall be used to interpret this dictionary password: The owner password o_value: A 32-byte string, based on both the owner and user passwords, that shall be used in computing the encryption key and in determining whether a valid owner password was entered oe_value: u_value: A 32-byte string, based on the user password, that shall be used in determining whether to prompt the user for a password and, if so, whether a valid user or owner password was entered. Returns: The key NrH(0r)c3 K|]}dywrNrFr.rds r'r0z.AlgV5.verify_owner_password..(i1i r{rcalculate_hashrrr@r )rrMrrr|ivtmp_keys r'rzAlgV5.verify_owner_passwords|DS>  Hgbngcrl Ks|  (eBi( (&&q(GBrNGCRLQwH55r)ue_valuec|dd}tj|||ddd|ddk7rytdtdD}tj|||ddd}t |||S) a# See :func:`verify_owner_password`. Args: R: A number specifying which revision of the standard security handler shall be used to interpret this dictionary password: The user password u_value: A 32-byte string, based on the user password, that shall be used in determining whether to prompt the user for a password and, if so, whether a valid user or owner password was entered. ue_value: Returns: bytes NrrHrr)c3 K|]}dywrrFrs r'r0z-AlgV5.verify_user_password..8rrr{rr)rrMr|rrrs r'r}zAlgV5.verify_user_password!sv(DS>   8WR^S AWSb\ Q (eBi( (&&q(GBrNCHwH55r)saltudatactj||z|zj}|dkr|Sd} |dz }||z|z}t|dd|dd|dz}tjtjtj ft |dddz}||j}|dk\r |d|dz krn|ddS) Nrrr{rH@rYr)r[sha256r_rsha384sha512sum) rrMrrkcountk1ehash_fns r'rzAlgV5.calculate_hash<s NN8d?U2 3 : : < q5H QJEA%B#2"R"r':A!CR&kAo G  !!#A{qu 2"v r)r;permsprSct|rdnd}tjd|dz|zdz}t||}||ddk(S)au See :func:`verify_owner_password` and :func:`compute_perms_value`. Args: key: The owner password perms: p: A set of flags specifying which operations shall be permitted when the document is opened with user access. If bit 2 is set to 1, all other bits are ignored and all operations are permitted. If bit 2 is set to 0, permission for operations are based on the values of the remaining flags defined in Table 24. metadata_encrypted: Returns: A boolean TFrUrWadbN )r]r^r)r;rrrSb8p1p2s r' verify_permszAlgV5.verify_permsQsI,(TT [[q !$7 7" .rrsecrets token_bytesrrrrr@r) rrMr; random_bytesval_saltkey_saltr|rrrs r'rxzAlgV5.compute_U_values6**2. ##&&q(HcBXMPXX&&q(HcB (eBi( ("7B4  r)c tjd}|dd}|dd}tj|||||z|z}tj||||dd}t dt dD} t || |} || fS)u Algorithm 3.9 Computing the encryption dictionary’s O (owner password) and OE (owner encryption key) values. 1. Generate 16 random bytes of data using a strong random number generator. The first 8 bytes are the Owner Validation Salt. The second 8 bytes are the Owner Key Salt. Compute the 32-byte SHA-256 hash of the password concatenated with the Owner Validation Salt and then concatenated with the 48-byte U string as generated in Algorithm 3.8. The 48-byte string consisting of the 32-byte hash followed by the Owner Validation Salt followed by the Owner Key Salt is stored as the O key. 2. Compute the 32-byte SHA-256 hash of the password concatenated with the Owner Key Salt and then concatenated with the 48-byte U string as generated in Algorithm 3.8. Using this hash as the key, encrypt the file encryption key using AES-256 in CBC mode with no padding and an initialization vector of zero. The resulting 32-byte string is stored as the OE key. Args: R: password: key: u_value: A 32-byte string, based on the user password, that shall be used in determining whether to prompt the user for a password and, if so, whether a valid user or owner password was entered. Returns: A tuple (O value, OE value) r{NrXrc3 K|]}dywrrFrs r'r0z(AlgV5.compute_O_value..rrr) rrMr;r|rrrrrrrs r'rtzAlgV5.compute_O_valuesF**2. ##  Hh @8 Kh V &&q(HgcrlK (eBi( ("7B4  r)c|rdnd}tjd}tjd|dz|zdz|z}t ||S)u Algorithm 3.10 Computing the encryption dictionary’s Perms (permissions) value. 1. Extend the permissions (contents of the P integer) to 64 bits by setting the upper 32 bits to all 1’s. (This allows for future extension without changing the format.) 2. Record the 8 bytes of permission in the bytes 0-7 of the block, low order byte first. 3. Set byte 8 to the ASCII value ' T ' or ' F ' according to the EncryptMetadata Boolean. 4. Set bytes 9-11 to the ASCII characters ' a ', ' d ', ' b '. 5. Set bytes 12-15 to 4 bytes of random data, which will be ignored. 6. Encrypt the 16-byte block using AES-256 in ECB mode with an initialization vector of zero, using the file encryption key as the key. The result (16 bytes) is stored as the Perms string, and checked for validity when the file is opened. Args: key: p: A set of flags specifying which operations shall be permitted when the document is opened with user access. If bit 2 is set to 1, all other bits are ignored and all operations are permitted. If bit 2 is set to 0, permission for operations are based on the values of the remaining flags defined in Table 24. metadata_encrypted: A boolean indicating if the metadata is encrypted. Returns: The perms value rrrVrUrWr)rrr]r^r)r;rrSrrrr9s r'rzAlgV5.compute_Perms_valuesPB(TT   #{{4#&99B>G"LsD))r)N)rCrDrErrrrrr}rrrdictrrtuplerxrtrrFr)r'rrs E6 E6E6*/E6;@E6KPE6 E6E6N6 66*/6;@6 664#eEe(  %(>B 4        !   c3h  *"!3"!%"!e"!eUl@S"!"!H+! +!+!&++!6;+! ue| +!+!Z#*#*3#*D#*U#*#*r)rceZdZdZdZdZy) PasswordTyperrrvN)rCrDrE NOT_DECRYPTED USER_PASSWORDOWNER_PASSWORDrFr)r'rrsMMNr)rc eZdZdZdZdZdZdZy)EncryptAlgorithm)rrvr)rvrY)rVrVr)r)rrrN)rCrDrERC4_40RC4_128AES_128 AES_256_R5AES_256rFr)r'rrs FGGJGr)rc@eZdZUeed<eed<eed<eed<eed<y)EncryptionValuesOUOEUEPermsN)rCrDrErr__annotations__rFr)r'rr s H H I I Lr)rceZdZdZdededededededed ed ed ed e e d dfdZ d efdZ de deded e fdZde deded e fdZede d efdZdeded efdZededededed ef dZedeeefd efdZdeeefd efdZded eeeffd Zded eeeffd!Zd"ed#e ed efd$Zd"ed#ed dfd%Zed&eded dfd'Zed(e d)eded dfd*Z!y)+ EncryptionaJ Collects and manages parameters for PDF document encryption and decryption. Args: V: A code specifying the algorithm to be used in encrypting and decrypting the document. R: The revision of the standard security handler. Length: The length of the encryption key in bits. P: A set of flags specifying which operations shall be permitted when the document is opened with user access entry: The encryption dictionary object. EncryptMetadata: Whether to encrypt metadata in the document. first_id_entry: The first 16 bytes of the file's original ID. StmF: The name of the crypt filter that shall be used by default when decrypting streams. StrF: The name of the crypt filter that shall be used when decrypting all strings in the document. EFF: The name of the crypt filter that shall be used when encrypting embedded file streams that do not have their own crypt filter specifier. values: Additional encryption parameters. VrLengthrQentryEncryptMetadatafirst_id_entryStmFStrFEFFvaluesr#Nc ||_||_||_|dzdz|_||_||_||_| |_| |_| r| n t|_ tj|_ d|_y)Nl)rrrrQrrRrrrrrrr_password_type_key) r&rrrrQrrrrrrrs r'r(zEncryption.__init__,sq  k/[0.'  28>N>P *88%) r)c<|jtjk7Sr%)rrr)r&s r' is_decryptedzEncryption.is_decryptedJs""l&@&@@@r)r*idnum generationcn|j|s|S|j||}|j|Sr%)_is_encryption_object_make_crypt_filterr-r&r*rrcfs r'r-zEncryption.encrypt_objectM8))#.J  $ $UJ 7  %%r)cn|j|s|S|j||}|j|Sr%)rrr?rs r'r?zEncryption.decrypt_objectUrr)cLt|ttttt fSr%)r1rrrrr)r*s r'rz Encryption._is_encryption_object]s&       r)ctjd|dd}tjd|dd}|jsJ|j}|jdk(rdn|jdz}|d||z|z}t j |}|jdt|dzd} |jd |jdt|dzd} |} |j|j| | | } |j|j| | | } |j|j| | | }t| | |S) u Algorithm 1: Encryption of data using the RC4 or AES algorithms. a) Obtain the object number and generation number from the object identifier of the string or stream to be encrypted (see 7.3.10, "Indirect Objects"). If the string is a direct object, use the identifier of the indirect object containing it. b) For all strings and streams without crypt filter specifier; treating the object number and generation number as binary integers, extend the original n-byte encryption key to n + 5 bytes by appending the low-order 3 bytes of the object number and the low-order 2 bytes of the generation number in that order, low-order byte first. (n is 5 unless the value of V in the encryption dictionary is greater than 1, in which case n is the value of Length divided by 8.) If using the AES algorithm, extend the encryption key an additional 4 bytes by adding the value “sAlT”, which corresponds to the hexadecimal values 0x73, 0x41, 0x6C, 0x54. (This addition is done for backward compatibility and is not intended to provide additional security.) c) Initialize the MD5 hash function and pass the result of step (b) as input to this function. d) Use the first (n + 5) bytes, up to a maximum of 16, of the output from the MD5 hash as the key for the RC4 or AES symmetric key algorithms, along with the string or stream data to be encrypted. If using the AES algorithm, the Cipher Block Chaining (CBC) mode, which requires an initialization vector, is used. The block size parameter is set to 16 bytes, and the initialization vector is a 16-byte random number that is stored as the first 16 bytes of the encrypted stream or string. Algorithm 3.1a Encryption of data using the AES algorithm 1. Use the 32-byte file encryption key for the AES-256 symmetric key algorithm, along with the string or stream data to be encrypted. Use the AES algorithm in Cipher Block Chaining (CBC) mode, which requires an initialization vector. The block size parameter is set to 16 bytes, and the initialization vector is a 16-byte random number that is stored as the first 16 bytes of the encrypted stream or string. The output is the encrypted data to be stored in the PDF file. zF:f% &,89I,JF:i( )!#B'-Bz(# $*,HZ& ',6x,@HZ( ),6x,@HZ( ) 66Q;*:4;;>>*JHZ& '*:4;;>>*JHZ& '-=dkk>O>O-PHZ) *r)c tj||j|j}tj |||j}tj ||j|j||j |j|j}tj||j|j}||_ ||j_ ||j_ yr%)rLrirrrtrerQrRrrxrrrr)r&rkrfrjrr;r|s r'r"zEncryption.compute_values_v4-s++NDFFDKKP''G  FF KK  FF NN   ''TVVT^^D   r)encryption_entryc h|jddk7r tdd|vr tdd}d}d}|jdd}|d vrtd |d |d k\r|d }|jdd}|jdd}|jd|}|dk7r||d}|dk7r||d}|dk7r||d}d}||vrtd|d||vrtd|d||vrtd|dtt|d}tt|d} |jdd} |jd} | | jnd} t } tt |dj| _tt |dj| _ |jd t j| _ |jd!t j| _ |jd"t j| _ t||| | | || ||||# S)$Nrrz1only Standard PDF encryption handler is availablez /SubFilterz/SubFilter NOT supported/V2rr)rrvrYrVrz Encryption V=z NOT supportedrVrr r r!z/EFFr)r r+rrz StmF Method z NOT supported!z StrF Method z EFF Method rrrrz/EncryptMetadataTrrrrr rrrrQrrrrrrr)getNotImplementedErrorrrr<rrr3rrrrrr) r)r stm_filter str_filter ef_filteralg_verfiltersallowed_methodsalg_rev perm_flagskey_bitsencrypt_metadatars r'readzEncryption.read@s    *k 9%C  + +%&@A A   "&&tQ/ / )% gYn&MN N a<&u-G)--g{CJ)--g{CJ(,,VZ@I[($Z08 [($Z08 K'#I.v6 FO0)L O*TUU0)L O*TUU/)K {/*RSSs,T23#/56 #'' 26+//0BC&6&B  " " "#(*:4*@APP(*:4*@APP$((0@0BCRR $((0@0BCRR '++H6F6HIXX ,)"  r)alg permissionsc|\}}}d\}}}|tjk(rd\}}}n(|tjtjfvrd\}}}t ||||d|d|||t  S)N)r+r+r+)rrr)rrrTr,)rrrrrr) r:r;rr2r5r7r/r0r1s r'makezEncryption.makes&)"(,?) J "** *0L -J I %002B2J2JK K0L -J I )"$  r))"rCrDrE__doc__rrrrrr rrr(rrr-r?rrrrr rrrrrrrrr'r"r9rr=rFr)r'rrsn0* * * *  *  ******)** *<AdA&)&C&S&Y&&)&C&S&Y&  9      =;=;=;=;~ ! !# !16 !DI !  ! !5#4uUCZ0\/%/E%2E,F/8%E%2E,F(2 22:3-2 2h u e PT &> /> > <> > @  ,/ AF   r)r)-r[rr]enumrrtypingrrrrpypdf._crypt_providersr r r r r rrrrr_utilsrgenericrrrrrrrrrrrIrrrJrLrrrrrrrFr)r'rDs6 --   #   00hH "5"U"\ \ ~ a*a*H 7 udG G r)