ecc.c data structures
kmagnum at gmail.com
Mon Dec 28 16:00:11 CET 2009
On Mon, Dec 28, 2009 at 8:13 AM, Sergi Blanch i Torné <sergi at calcurco.cat>wrote:
> 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
> the ecc module by now, wherever in the future), but this gives me a crossed
> dependency that can be an issue.
Not having looked at the code in question, can't you just inject the
dependency by having the libgcrypt function take a function pointer to a
fingerprinting function as one of its arguments? This unfortunately means
libgcrypt has to have some vague notion about the fingerprint, but perhaps
the semantics can be kept sufficiently general to mitigate the ugliness of
forcing a higher-level concept down into libgcypt.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gcrypt-devel