The nightly gpgme newbie question: en- and decrypt problems

nico-gnupg-dev-0 at nico-gnupg-dev-0 at
Sun Jul 6 15:08:05 CEST 2008

Yeah, found the problem!

When I use gpgme_data_new_from_file() and import the result from
my previous encryption, it works:;a=commitdiff;h=37e753ff82232c2381e72e8c591eb1f4ce9bd962;hp=389a52942c1bb15183f747dc2902b641fe92b865

So after I removed the gpgme_data_write() call, it works:;a=commitdiff;h=25ae82d55031ca9fc8c8fa3c98af5c135ef5c7b3;hp=37e753ff82232c2381e72e8c591eb1f4ce9bd962

Now I've only to find out, what I made wrong in that call...


ps: GPGME_DEBUG is nice, but not so helpful.

Werner Koch [Thu, Jun 26, 2008 at 11:42:06PM +0200]:
> On Thu, 26 Jun 2008 23:00, nico-gnupg-dev-0 at said:
> > But shouldn't it contain data, if gpgme_op_encrypt() before was successful?
> Run your test program like 
> GPGME_DEBUG=9:/tmp/foo.log ./test
> and check the pretty verbose log to see the data excahnged between gpgme
> and gpg.
> Salam-Shalom,
>    Werner
> -- 
> Die Gedanken sind frei.  Auschnahme regelt ein Bundeschgesetz.

Think about Free and Open Source Software (FOSS).

PGP: BFE4 C736 ABE5 406F 8F42  F7CF B8BE F92A 9885 188C
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: </pipermail/attachments/20080706/10ddeb5a/attachment.pgp>

More information about the Gnupg-devel mailing list