Foxit PDF SDK
|
Public Member Functions | |
RMSSecurityHandler () | |
Constructor. More... | |
RMSSecurityHandler (SecurityHandler other) | |
Constructor, with parent class object. More... | |
bool | Initialize (RMSEncryptData encrypt_data, RMSSecurityCallback callback) |
Initialize current Microsoft RMS security handler. More... | |
![]() | |
SecurityHandler () | |
Constructor. | |
SecurityHandler (SecurityHandler other) | |
Constructor, with another security handler object. More... | |
virtual PDFDoc.EncryptType | GetSecurityType () |
Get the encryption type of current security handler. More... | |
bool | IsEmpty () |
Check whether current object is empty or not. More... | |
Additional Inherited Members | |
![]() | |
enum | CipherType { CipherType.e_CipherNone = 0, CipherType.e_CipherRC4 = 1, CipherType.e_CipherAES = 2 } |
Enumeration for Encryption Algorithm. More... | |
This class represents a RMS security handler, used for RMS encryption.
|
inline |
Constructor.
|
inline |
Constructor, with parent class object.
[in] | other | Parent class object. |
|
inline |
Initialize current Microsoft RMS security handler.
If this function is successfully, Foxit PDF SDK will take over the input security callback object and user should not release this callback object directly anymore; otherwise unexpected crash may occurs later.
Foxit PDF SDK may release the security callback object by callback function SecurityCallback.Release (inherited from RMSSecurityCallback's parent class), when current security handler is released and find that the callback object has not been used by other object. So, user is recommended not to use the security callback object any more, after current security handler is released.
[in] | encrypt_data | A RMS encrypt data object. |
[in] | callback | A valid RMSSecurityCallback object, which is inherited and implemented by user for their own encryption and description algorithm. It should not be null. |