verify and recover
marcus.brinkmann at ruhr-uni-bochum.de
Mon Mar 16 15:06:52 CET 2009
Oguz Yarimtepe wrote:
>> So, depending on detached or inline signature, you have to invoke it with
>> different paramters. gpgme/tests/gpg/ contains example code.
> I had checked the example before but after i read your explanation i
> fixed my code. I had to comment the summary part at the check_result
> function (line 94 shows nil). One of the question i want to ask is
> whether every signature has a summary or not?
The test suite contains example code and regression tests. The regression
tests are of course not very useful for your own code.
Every sig has a summary, which uses the validity of the key in the keyring and
the signature status to give an indication (green, yellow, red) for the
signature that is usable in common applications such as mail user agents.
> Second i realized i need to have at least the file, that is the original
> unsigned and not encrypted file, size of memory both for
> gpgme_op_verify(ctx, in, NULL, out) and gpgme_op_decrypt_verify(ctx, in,
> out) work correctly.
> Is it possible to make them work also at lesser memory size or is it
> required some new implementation of code?
I don't really understand what you are asking here. If you do not want to
store the result in memory, you can use other gpgme_data_t objects, such as
one based on a file descriptor, file handle, or user callback.
More information about the Gnupg-devel