[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: crypto engine
From: |
Nikos Mavrogiannopoulos |
Subject: |
Re: crypto engine |
Date: |
Tue, 06 May 2008 18:00:46 +0300 |
User-agent: |
Thunderbird 2.0.0.12 (X11/20080227) |
Nikos Mavrogiannopoulos wrote:
>> do this instead:
>>
>> typedef int (*gnutls_rng_init_func)( void** ctx);
>> typedef int (*gnutls_rng_rnd_func) ( void* ctx, gnutls_rnd_level_t level,
>> void* data, int datasize);
>> typedef void (*gnutls_rng_deinit_func)( void* ctx);
>>
>> int gnutls_crypto_rnd_register( int priority,
>> gnutls_rng_init_func init,
>> gnutls_rng_rnd_func rnd,
>> gnutls_rng_deinit_func deinit);
>
> I'm really thinking doing this. The only bad thing is that because of
> the many functions that need to be registered the API would be quite
> ugly, but anyway it would allow us to maintain a stable api.
And it is seems that the API is quite ugly and cumbersome to use (such
as a function with 24 arguments). I'll keep the current struct based API
but I'll added some versioning information in the registration functions
to avoid modifying a structure with different version.
- Re: crypto engine, Nikos Mavrogiannopoulos, 2008/05/06
- Re: crypto engine,
Nikos Mavrogiannopoulos <=