unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon Josefsson <simon@josefsson.org>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: gnus/starttls.el and net/tls.el
Date: Thu, 08 Nov 2007 14:35:12 +0100	[thread overview]
Message-ID: <87tznwq2r3.fsf@mocca.josefsson.org> (raw)
In-Reply-To: <E1Ipflm-0004Yx-6I@fencepost.gnu.org> (Richard Stallman's message of "Wed, 07 Nov 2007 02:56:14 -0500")

(I'm cc'ing emacs-devel since there appears to be other threads
discussing this already.)

Richard Stallman <rms@gnu.org> writes:

> Can you tell me how these two files relate to each other?

They both create a TLS encrypted network socket using external tools,
but there is some differences:

tls.el starts talking TLS to the server directly.  starttls.el, however,
does not begin talking TLS until the application calls
starttls-negotiate.  In other words, starttls.el allows an unencrypted
phase before the encrypted phase starts.

tls.el can use openssl and gnutls.  starttls.el can use gnutls and a
tool called 'starttls'.

They serve (slightly) different purposes, but there is some code
duplication.  They probably should be merged eventually, but it requires
some effort (especially testing on many operating systems) and I'm
afraid I don't have time to work on it.

/Simon

       reply	other threads:[~2007-11-08 13:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1Ipflm-0004Yx-6I@fencepost.gnu.org>
2007-11-08 13:35 ` Simon Josefsson [this message]
2007-11-09 22:00   ` gnus/starttls.el and net/tls.el Richard Stallman
2007-11-15 14:20     ` Simon Josefsson
2007-11-16  4:29       ` Richard Stallman
2007-11-26 15:28         ` Simon Josefsson
2007-11-26 22:39           ` Richard Stallman
2007-11-28 13:44           ` Sascha Wilde
2007-11-29 11:34             ` Simon Josefsson
2007-11-29 12:08               ` Sascha Wilde

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=87tznwq2r3.fsf@mocca.josefsson.org \
    --to=simon@josefsson.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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).