From: Richard Stallman <rms@gnu.org>
Cc: wmperry@gnu.org, emacs-devel@gnu.org
Subject: Re: Another update of GNU TLS bindings
Date: Mon, 25 Feb 2002 09:23:29 -0700 (MST) [thread overview]
Message-ID: <200202251623.g1PGNT915882@aztec.santafe.edu> (raw)
In-Reply-To: <ilun0xyrbfk.fsf@extundo.com> (message from Simon Josefsson on Sun, 24 Feb 2002 19:18:07 +0100)
GNUTLS is a library, OpenSSL is both a library and an application.
William's ssl.el invokes the binary. This is a inflexible method, it
is complicated to find out what algorithms chosed during the TLS
handshake, and generally difficult to do anything interactive during
the TLS handshake.
I see why that method is not as flexible. But it is nonetheless a
useful alternative. If OpenSSL can do it, why can't we do it?
Even if GNUTLS shipped with a binary allowing it to do all the things
OpenSSL currently does, it would not be satisfactory.
Would this method be less satisfactory for GNUTLS than it is for OpenSSL?
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-02-25 16:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0202220939320.7021-100000@yxa.extundo.com>
2002-02-23 20:21 ` Another update of GNU TLS bindings Richard Stallman
2002-02-23 20:27 ` Simon Josefsson
2002-02-24 17:58 ` Richard Stallman
2002-02-24 18:18 ` Simon Josefsson
2002-02-25 16:23 ` Richard Stallman [this message]
2002-02-25 20:34 ` Simon Josefsson
2002-02-26 20:15 ` Richard Stallman
[not found] <iluofj6a0j9.fsf@dhcp133.extundo.com>
2002-02-07 14:56 ` Richard Stallman
2002-02-21 14:32 ` William M. Perry
[not found] ` <200202040736.JAA08217@is.elta.co.il>
2002-02-07 14:58 ` Richard Stallman
2002-02-07 17:36 ` Simon Josefsson
2002-02-08 23:23 ` Richard Stallman
2002-02-09 12:29 ` Simon Josefsson
2002-02-11 2:08 ` Richard Stallman
2002-02-13 8:50 ` Florian Weimer
2002-02-10 5:17 ` Richard Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200202251623.g1PGNT915882@aztec.santafe.edu \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=wmperry@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.