MemberManagement/bin/Debug/NPOI.OOXML.xml

这里只显示每个文件的开头 60 行。登录后可以解锁完整代码。

微信扫码关注公众号，代码整理好后第一时间通知你。

<?xml version="1.0"?>
<doc>
    <assembly>
        <name>NPOI.OOXML</name>
    </assembly>
    <members>
        <member name="T:NPOI.POIFS.Crypt.Agile.AgileDecryptor">
            Decryptor implementation for Agile Encryption
        </member>
        <member name="M:NPOI.POIFS.Crypt.Agile.AgileDecryptor.VerifyPassword(System.String)">
            Set decryption password
        </member>
        <member name="M:NPOI.POIFS.Crypt.Agile.AgileDecryptor.VerifyPassword(NPOI.POIFS.Crypt.Agile.KeyPair,Org.BouncyCastle.X509.X509Certificate)">
             instead of a password, it's also possible to decrypt via certificate.
             Warning: this code is experimental and hasn't been validated
             
             @see <a href="http://social.msdn.microsoft.com/Forums/en-US/cc9092bb-0c82-4b5b-ae21-abf643bdb37c/agile-encryption-with-certificates">Agile encryption with certificates</a>
            
             @param keyPair
             @param x509
             @return true, when the data can be successfully decrypted with the given private key
             @throws GeneralSecurityException
        </member>
        <member name="T:NPOI.POIFS.Crypt.Agile.AgileDecryptor.AgileCipherInputStream">
            2.3.4.15 Data Encryption (Agile Encryption)
            
            The EncryptedPackage stream (1) MUST be encrypted in 4096-byte segments to facilitate nearly
            random access while allowing CBC modes to be used in the encryption Process.
            The Initialization vector for the encryption process MUST be obtained by using the zero-based
            segment number as a blockKey and the binary form of the KeyData.saltValue as specified in
            section 2.3.4.12. The block number MUST be represented as a 32-bit unsigned integer.
            Data blocks MUST then be encrypted by using the Initialization vector and the intermediate key
            obtained by decrypting the encryptedKeyValue from a KeyEncryptor Contained within the
            KeyEncryptors sequence as specified in section 2.3.4.10. The data block MUST be pAdded to
            the next integral multiple of the KeyData.blockSize value. Any pAdding bytes can be used. Note
            that the StreamSize field of the EncryptedPackage field specifies the number of bytes of
            unencrypted data as specified in section 2.3.4.4.
        </member>
        <member name="T:NPOI.POIFS.Crypt.Agile.AgileEncryptionVerifier">
            Used when Checking if a key is valid for a document 
        </member>
        <member name="M:NPOI.POIFS.Crypt.Agile.AgileEncryptor.UpdateIntegrityHMAC(System.IO.FileInfo,System.Int32)">
             Generate an HMAC, as specified in [RFC2104], of the encrypted form of the data (message), 
             which the DataIntegrity element will verify by using the Salt generated in step 2 as the key. 
             Note that the entire EncryptedPackage stream (1), including the StreamSize field, MUST be 
             used as the message.
             
             Encrypt the HMAC as in step 3 by using a blockKey byte array consisting of the following bytes:
             0xa0, 0x67, 0x7f, 0x02, 0xb2, 0x2c, 0x84, and 0x33.
            
        </member>
        <member name="T:NPOI.POIFS.Crypt.Agile.AgileEncryptor.AgileCipherOutputStream">
            2.3.4.15 Data Encryption (Agile Encryption)
            
            The EncryptedPackage stream (1) MUST be encrypted in 4096-byte segments to facilitate nearly
            random access while allowing CBC modes to be used in the encryption Process.
            The Initialization vector for the encryption process MUST be obtained by using the zero-based
            segment number as a blockKey and the binary form of the KeyData.saltValue as specified in
            section 2.3.4.12. The block number MUST be represented as a 32-bit unsigned integer.
            Data blocks MUST then be encrypted by using the Initialization vector and the intermediate key