ecc.c data structures

Sergi Blanch i Torné sergi at
Mon Dec 28 14:13:47 CET 2009

On Monday 28 December 2009 01:56:48 pm you wrote:
> On Mon, 28 Dec 2009 12:03:25 +0100, Sergi Blanch i Torné wrote:
> > Param = curve_OID_len || curve_OID || public_key_alg_ID ||
> >            01 || KDF_hash_ID || AES_alg_ID for AESKeyWrap ||
> >           "AnonymousSender" || recipient_fingerprint
> That is all in GnuPG.  fingerprint_from_pk ().

First idea that comes to my mean now is to use gnupg as a lib in the kdf (in 
the ecc module by now, wherever in the future), but this gives me a crossed 
dependency that can be an issue.

GnuPG uses libgcrypt as crypto and mathematics library, isn't it? But I cannot 
see clearly that can be accepted in libgcrypt that it uses GnuPG as a lib.

About the other question I made. What about the structs? Can be good to extend 
the mpi_ec_ctx_s with the data that is used in some places? or it's better to 
have a third struct specific for encrypt algorithm?


More information about the Gcrypt-devel mailing list