#include <signencryptjob.h>

Signals | |
void | result (const GpgME::SigningResult &signingresult, const GpgME::EncryptionResult &encryptionresult, const TQByteArray &cipherText) |
![]() | |
void | progress (const TQString &what, int current, int total) |
void | done () |
Public Member Functions | |
virtual GpgME::Error | start (const std::vector< GpgME::Key > &signers, const std::vector< GpgME::Key > &recipients, const TQByteArray &plainText, bool alwaysTrust=false)=0 |
virtual std::pair< GpgME::SigningResult, GpgME::EncryptionResult > | exec (const std::vector< GpgME::Key > &signers, const std::vector< GpgME::Key > &recipients, const TQByteArray &plainText, bool alwaysTrust, TQByteArray &cipherText)=0 |
![]() | |
virtual void | showErrorDialog (TQWidget *parent=0, const TQString &caption=TQString()) const |
virtual TQString | auditLogAsHtml () const |
virtual GpgME::Error | auditLogError () const |
bool | isAuditLogSupported () const |
Protected Member Functions | |
SignEncryptJob (TQObject *parent, const char *name) | |
![]() | |
Job (TQObject *parent, const char *name) | |
Additional Inherited Members | |
![]() | |
virtual void | slotCancel ()=0 |
Detailed Description
An abstract base class for asynchronous combined signing and encrypting.
To use a SignEncryptJob, first obtain an instance from the CryptoBackend implementation, connect the progress() and result() signals to suitable slots and then start the operation with a call to start(). This call might fail, in which case the SignEncryptJob instance will have scheduled it's own destruction with a call to TQObject::deleteLater().
After result() is emitted, the SignEncryptJob will schedule it's own destruction by calling TQObject::deleteLater().
Definition at line 67 of file signencryptjob.h.
Member Function Documentation
◆ start()
|
pure virtual |
Starts the combined signing and encrypting operation.
signers is the list of keys to sign plainText with. recipients is a list of keys to encrypt the signed plainText to. In both lists, empty (null) keys are ignored.
If alwaysTrust is true, validity checking for the recipient keys will not be performed, but full validity assumed for all recipient keys without further checks.
The documentation for this class was generated from the following file: