From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: emacs-devel@gnu.org
Subject: Re: url library and GnuTLS, and Emacs-issued certificates
Date: Thu, 24 Mar 2011 05:55:30 +0100 [thread overview]
Message-ID: <m34o6ti0cd.fsf@quimbies.gnus.org> (raw)
In-Reply-To: 87ei5xo695.fsf@stupidchicken.com
Chong Yidong <cyd@stupidchicken.com> writes:
> Could you explain in more detail?
tls.el is quite simple. You start openssl/gnutls-cli as a subprocess
with the correct parameters, parse the output slightly, and then talk
over the socket.
starttls.el is a bit different. You call `open-starttls-stream', which
starts gnutls-cli in unencrypted mode. Then you do protocol-specific
things to see whether the server supports STARTTLS. If it does, you
issue the commands necessary for the server to start talking TLS. You
then call `startls-negotiate' which sends a signal to gnutls-cli which
makes gnutls-cli go to encrypted mode, parses the output from
gnutls-cli, and returns the status of the now-encrypted socket.
To make things even more confusing, openssl does have support for
STARTTLS, too, but you then have to let openssl itself do the STARTTLS
negotiation by telling openssl what protocol it's talking. And it
doesn't support all the protocols that Emacs needs, so it can't really
be used.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2011-03-24 4:55 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-19 16:21 expand tls to elpa.gnu.org axel.junker
2011-03-21 18:28 ` Ted Zlatanov
2011-03-21 21:17 ` Chong Yidong
2011-03-21 22:33 ` url library and GnuTLS, and Emacs-issued certificates (was: expand tls to elpa.gnu.org) Ted Zlatanov
2011-03-23 15:30 ` url library and GnuTLS, and Emacs-issued certificates Ted Zlatanov
2011-03-23 18:31 ` Chong Yidong
2011-03-23 18:47 ` Ted Zlatanov
2011-03-23 19:20 ` Lars Magne Ingebrigtsen
2011-03-23 21:51 ` Chong Yidong
2011-03-24 4:55 ` Lars Magne Ingebrigtsen [this message]
2011-03-24 18:42 ` Chong Yidong
2011-03-24 19:45 ` Lars Magne Ingebrigtsen
2011-03-24 19:23 ` Chong Yidong
2011-03-24 19:33 ` Ted Zlatanov
2011-03-24 19:37 ` Lars Magne Ingebrigtsen
2011-03-26 23:32 ` Chong Yidong
2011-03-26 23:39 ` Lars Magne Ingebrigtsen
2011-03-27 1:23 ` Chong Yidong
2011-03-27 10:31 ` Lars Magne Ingebrigtsen
2011-03-27 0:20 ` Lars Magne Ingebrigtsen
2011-03-27 1:30 ` Chong Yidong
2011-03-27 10:36 ` Lars Magne Ingebrigtsen
2011-03-27 17:42 ` Chong Yidong
2011-03-28 0:34 ` Chong Yidong
2011-03-29 20:54 ` Lars Magne Ingebrigtsen
2011-03-30 2:20 ` Chong Yidong
2011-03-26 12:07 ` Ted Zlatanov
2011-03-26 13:39 ` Reiner Steib
2011-03-26 14:09 ` Ted Zlatanov
2011-03-28 6:51 ` Reiner Steib
2011-03-26 19:40 ` Tom Tromey
2011-03-26 23:36 ` Chong Yidong
2011-03-27 1:31 ` Tom Tromey
2011-03-27 1:52 ` Chong Yidong
2011-03-28 15:10 ` Ted Zlatanov
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m34o6ti0cd.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=emacs-devel@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).