On Wed, 12 Jun 2002, Hrvoje Niksic wrote:
Ok, IANAL and I won't stress this as there's probably something here that my
little brain hasn't understood.
- Just make your extension a library and name it OpenSSL.
- Or just extend the existing OpenSSL library to do whatever things you
Hi,
was the patch for switching to GNUTLS been tested yet ?
If only done some quick checks, (work with/out http(s)) so that
it is usable, but need to test client cert sending and server cert checking.
I ask because this would solve the whole openssl problem, or most of it.
Cu Thomas Lußnig
On Thu, 13 Jun 2002, Thomas Lussnig wrote:
was the patch for switching to GNUTLS been tested yet ?
If only done some quick checks, (work with/out http(s)) so that
it is usable, but need to test client cert sending and server cert checking.
I ask because this would solve the whole openssl
Daniel Stenberg [EMAIL PROTECTED] writes:
Yes
If the big bad company wants to use wget and modify it for their own purposes
without giving the source code back, the recently added exception to the GPL
gives them every means:
- Just make your extension a library and name it OpenSSL.
-
Yes
If the big bad company wants to use wget and modify it for their own purposes
without giving the source code back, the recently added exception to the GPL
gives them every means:
- Just make your extension a library and name it OpenSSL.
- Or just extend the existing OpenSSL library to do
Daniel Stenberg wrote:
Yes
If the big bad company wants to use wget and modify it for their own purposes
without giving the source code back, the recently added exception to the GPL
gives them every means:
- Just make your extension a library and name it OpenSSL.
- Or just extend the
