certmanager/lib

Kleo::VerifyOpaqueJob Class Referenceabstract

#include <verifyopaquejob.h>

Inheritance diagram for Kleo::VerifyOpaqueJob:
Kleo::Job

Signals

void result (const GpgME::VerificationResult &result, const TQByteArray &plainText)
 
- Signals inherited from Kleo::Job
void progress (const TQString &what, int current, int total)
 
void done ()
 

Public Member Functions

virtual GpgME::Error start (const TQByteArray &signedData)=0
 
virtual GpgME::VerificationResult exec (const TQByteArray &signedData, TQByteArray &plainText)=0
 
- Public Member Functions inherited from Kleo::Job
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

 VerifyOpaqueJob (TQObject *parent, const char *name)
 
- Protected Member Functions inherited from Kleo::Job
 Job (TQObject *parent, const char *name)
 

Additional Inherited Members

- Public Slots inherited from Kleo::Job
virtual void slotCancel ()=0
 

Detailed Description

An abstract base class for asynchronous verification of opaque signatures.

To use a VerifyOpaqueJob, first obtain an instance from the CryptoBackend implementation, connect the progress() and result() signals to suitable slots and then start the verification with a call to start(). This call might fail, in which case the VerifyOpaqueJob instance will have scheduled it's own destruction with a call to TQObject::deleteLater().

After result() is emitted, the VerifyOpaqueJob will schedule it's own destruction by calling TQObject::deleteLater().

Definition at line 62 of file verifyopaquejob.h.

Member Function Documentation

◆ exec()

virtual GpgME::VerificationResult Kleo::VerifyOpaqueJob::exec ( const TQByteArray &  signedData,
TQByteArray &  plainText 
)
pure virtual

Synchronous version of start.

◆ start()

virtual GpgME::Error Kleo::VerifyOpaqueJob::start ( const TQByteArray &  signedData)
pure virtual

Starts the verification operation.

signature contains the signature data, while signedData contains the data over which the signature was made.


The documentation for this class was generated from the following file: