unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: Tuning GnuTLS
Date: Thu, 27 Oct 2011 18:12:45 -0400	[thread overview]
Message-ID: <87bot2axsy.fsf@lifelogs.com> (raw)
In-Reply-To: 87pqikpo6v.fsf@lifelogs.com

On Wed, 28 Sep 2011 12:32:56 -0500 Ted Zlatanov <tzz@lifelogs.com> wrote: 

TZ> On Mon, 18 Jul 2011 05:23:16 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote: 
LMI> We should strive to make TLS connections as painless as possible, and
LMI> involving as little user intervention as possible, while preserving a
LMI> reasonable level of security.

LMI> So far, two failure points have been identified:

LMI> 1) Some servers sends a prime with fewer bits than the accepted default.
LMI> I think the right thing to do here is to just default
LMI> `gnutls-min-prime-bits' to a lower number than the default GnuTLS
LMI> number.  I don't know what that number should be, but I think people who
LMI> want better bits than that can adjust this number upwards.

LMI> 2) Servers presenting broken, er, certificates with certain algorithms.
LMI> If negotiation with DHE-RSA has failed, then negotiation without that
LMI> algorithm should be attempted.  But is it possible to fall back to
LMI> plain-text?  I don't really know how that works.  But if that's
LMI> possible, the fall-back should obviously stop before it gets that far.

LMI> After a priority has been established, I then think that the priority
LMI> for this specific server/port pair should be saved via Customize, so
LMI> that the next connection can be done faster automatically, without the
LMI> need for all this negotiation.

TZ> Could you ask on the GnuTLS dev list?  Both of these are possible AFAICT
TZ> but perhaps they have suggestions for the implementation specifics.

Ping? I haven't seen anything on the GnuTLS dev list.  Do you want me to
ask?

Thanks
Ted




  parent reply	other threads:[~2011-10-27 22:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-18  3:23 Tuning GnuTLS Lars Magne Ingebrigtsen
2011-09-28 17:32 ` Ted Zlatanov
2011-10-06 19:07   ` Lars Magne Ingebrigtsen
2011-10-10 21:46     ` Ted Zlatanov
2011-10-27 22:12   ` Ted Zlatanov [this message]
2011-11-03 20:12     ` Lars Magne Ingebrigtsen

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=87bot2axsy.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --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).