gnutls-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GnuTLS 3.0.0 released


From: Nikos Mavrogiannopoulos
Subject: Re: GnuTLS 3.0.0 released
Date: Mon, 15 Aug 2011 22:37:56 +0200
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110617 Thunderbird/3.1.11

On 08/15/2011 07:08 PM, Andreas Metzler wrote:
> On 2011-07-29 Nikos Mavrogiannopoulos <address@hidden> wrote:
> [...]
>> ** libgnutls: license upgraded to LGPLv3
> 
> Hello,
> The guile-wrapper is still LGPLv2.1+ / GPLv2+, was this intended?

Hello Andreas,
 They should have been updated in head to the LGPLv3 as well.

> [...]
> This is compared to 2.10, not 2.12, isn't it? Both 2.12.7 and 3.0.0
> use the same soname for the ssl wrapper and at a quick glance this
> seems to be the only interesting change:
> --- gnutls-2.12.7/libextra/includes/gnutls/openssl.h    2011-04-08 
> 02:30:45.000000000 +0200
> +++ gnutls-3.0.0/libextra/includes/gnutls/openssl.h     2011-05-07 
> 23:32:29.000000000 +0200
> @@ -100,7 +100,7 @@ extern "C"
>    typedef struct
>    {
>      char priority_string[256];
> -    gnutls_connection_end_t connend;
> +    unsigned int connend;
>    } SSL_METHOD;
> gnutls_connection_end_t was a enum in 2.12.7, does this change the
> size of the struct?

Interesting. I don't remember why this wasn't included in the 0.12.x
version. Although it is not a strict C requirement, enumerations have
the same size as integers in most compilers (including gcc) and thus
they are binary compatible.

> [...]
>> ** libgnutls-extra: Inner application extension was removed.
>> It was never standardized nor published as an RFC.
> [...]
> So extra is an empty shell now, isn't it? 

Indeed.

> Sholulds the gcrypt related code be reomved from gnutls_extra.c?

I'll keep it for a while just in case someone volunteers to update
the gcrypt code (currently it is impossible since gcrypt doesn't
have GCM that is now required but it might be available later).

best regards,
Nikos



reply via email to

[Prev in Thread] Current Thread [Next in Thread]