Strange gpgme_sigsum_t value in gpgme (bug?)
marcus.brinkmann at ruhr-uni-bochum.de
Thu Jun 16 17:37:58 CEST 2011
On 06/14/2011 07:54 PM, Matthias Klumpp wrote:
> On Tue, 14 Jun 2011 13:39:45 -0400, Daniel Kahn Gillmor
> <dkg at fifthhorseman.net> wrote:
>> On 06/14/2011 12:32 PM, Matthias Klumpp wrote:
>>> I'm new to GPGMe, so this maybe is a foolish question, but I stumbled
>>> a very weird behavior of GPGMe, which cause my application to act very,
>>> very weird :P
>>> Is this a bug, or am I just doing it wrong?
>> I believe the field is a bitfield, so the flags are additive.
>> 0x03 == 0x02 + 0x01
>> So that means GPGME_SIGSUM_VALID + GPGME_SIGSUM_GREEN
> Oo... Thanks! I'm using GPGMe via Vala, maybe this brought me on the wrong
> track (the vapi file for GPGMe is buggy, I'm ficing it at time)
> Sorry for the noise and thanks again for your help!
Well, in a sense, it's my fault, too, I shouldn't have made it an enum in the
first place, but just constant #defines.
More information about the Gnupg-devel