how to use libgcrypt library
Wed, 23 Jul 2003 11:54:55 -0700
Content-Type: text/plain; charset=US-ASCII; format=flowed
On Wednesday, Jul 23, 2003, at 11:03 US/Pacific, Moritz Schulte wrote:
> Neil Spring <firstname.lastname@example.org> writes:
>> There's also a newer, nicer interface in CVS; I chose to avoid it
>> and use the existing stuff.
> I'm just curious - why?
No particularly insightful reason; first, the _pk_ functions are
available today in 1.1.12, so I can build my code on my Debian and OS X
systems without reconfiguring. Second, they seemed better documented
-- indeed, tests/pubkey.c was useful, though it did not include a
sign/verify test. Third, and least important, the manual's
introduction of the _ac_ functions read like they were for wimps who
couldn't be bothered to learn s-expressions, so my ego took over <grin>.
That said, if 1.1.13 were released yesterday and ac.c signed plaintext
(check_run has an unused variable "s" that looks like it is for this
purpose), I probably would have trusted that _ac_ was easier and made a
> While having a quick look at your example code, I noticed that you use
> an `int' variable for error values, although `gcry_error_t' is a
> better choice.
> Btw, in CVS there's also tests/pubkey.c, which shows how to use
> ((gpg-key-id . "6F984199")
> (email . "email@example.com")
> (webpage . "http://duesseldorf.ccc.de/~moritz/"))
> Gcrypt-devel mailing list
content-type: application/pgp-signature; x-mac-type=70674453;
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (Darwin)
-----END PGP SIGNATURE-----