In message <[EMAIL PROTECTED]> on Wed, 29 Jun 2005 22:05:07 -0700, Dan Kegel 
<[EMAIL PROTECTED]> said:

dank> http://www.gnu.org/software/gnutls/
dank> exposes two APIs: the OpenSSL api (I gather?), and its own.

About the OpenSSL API, this page answers part of the question.

  http://www.gnu.org/software/gnutls/reference/gnutls-openssl.html

The rest of the answer is in gnutls/openssl.h.  They expose some
structures to remain compatible with the way OpenSSL currently works,
so it's basically a compatibility that's as stripped down as
possible.

For the rest of GnuTLS, they seem to expose very little, from what I
can gather by looking at the public header files.

dank> If so, perhaps that might provide a way forward: apps that need
dank> a stable interface can use the gnutls api (which openssl could
dank> provide as a wrapper); everyone else could use the openssl api
dank> (which gnutls seems to provide as a wrapper, unless I misread
dank> the docs).

It's a path.  Just a small warning about license politics: According
to http://www.gnu.org/software/gnutls/gnutls.html, the GnuTLS core
library is licensed under the LGPL.  Looking at the header files, it
looks like there's a mix of GPL and LGPL, and among others, their
openssl.h is under the GPL (something I find very interesting).  This
may have changed with later versions...

Cheers,
Richard

-----
Please consider sponsoring my work on free software.
See http://www.free.lp.se/sponsoring.html for details.

-- 
Richard Levitte                         [EMAIL PROTECTED]
                                        http://richard.levitte.org/

"When I became a man I put away childish things, including
 the fear of childishness and the desire to be very grown up."
                                                -- C.S. Lewis
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       openssl-dev@openssl.org
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to