certmanager/lib
Kleo::VerifyOpaqueJob Class Reference
An abstract base class for asynchronous verification of opaque signatures. More...
#include <verifyopaquejob.h>
Inheritance diagram for Kleo::VerifyOpaqueJob:

Signals | |
void | result (const GpgME::VerificationResult &result, const QByteArray &plainText) |
Public Member Functions | |
virtual GpgME::Error | start (const QByteArray &signedData)=0 |
virtual GpgME::VerificationResult | exec (const QByteArray &signedData, QByteArray &plainText)=0 |
Protected Member Functions | |
VerifyOpaqueJob (QObject *parent, const char *name) |
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 QObject::deleteLater().
After result() is emitted, the VerifyOpaqueJob will schedule it's own destruction by calling QObject::deleteLater().
Definition at line 62 of file verifyopaquejob.h.
Member Function Documentation
virtual GpgME::VerificationResult Kleo::VerifyOpaqueJob::exec | ( | const QByteArray & | signedData, | |
QByteArray & | plainText | |||
) | [pure virtual] |
Synchronous version of start.
virtual GpgME::Error Kleo::VerifyOpaqueJob::start | ( | const QByteArray & | 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: