Re: TODO: GNU TLS

From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: mark(at)mark(dot)mielke(dot)cc, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: TODO: GNU TLS
Date: 2006-12-28 22:47:35
Message-ID: 20061228224735.GB9484@svana.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Dec 28, 2006 at 05:16:58PM -0500, Andrew Dunstan wrote:
> I agree with this comment from Steve Langasek at
> http://lists.debian.org/debian-legal/2003/01/msg00022.html :
>
> >Sure, code can be rewritten to use gnutls natively. But I don't
> >understand why anyone would consider this a useful expenditure of
> >developer resources when the necessary OpenSSL compat glue could simply
> >be made available under the LGPL.
>
> If this is such an issue, why hasn't somebody done that?

Maybe because the OpenSSL interface is terrible? I'm not sure if it's
actually possible to emulate the OpenSSL interface, given the way the
libraries work internally are completely different.

There is an OpenSSL compatability layer, but postgres won't compile
with it because it's nowhere near complete enough, even for the simple
things postgres wants to do.

However, in this case we're talking about code that has already been
written. So the work has already been done...

Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2006-12-28 23:01:03 Re: Recent SIGSEGV failures in buildfarm HEAD
Previous Message Simon Riggs 2006-12-28 22:47:23 Re: pg_standby