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: Additional network security
Date: Sat, 20 Dec 2014 06:27:25 -0500	[thread overview]
Message-ID: <87tx0qsgrm.fsf@lifelogs.com> (raw)
In-Reply-To: 87r3vwaajz.fsf@marauder.physik.uni-ulm.de

On Thu, 18 Dec 2014 22:54:24 +0100 Reiner Steib <reinersteib+gmane@imap.cc> wrote: 

RS> Lars Magne Ingebrigtsen wrote:
>> Ted Zlatanov <tzz@lifelogs.com> writes:
>> 
>>> How about extending the GnuTLS priority string to also specify the NSM
>>> level, DH bits, etc? So the user would say "NORMAL:NSM(medium,dh=1024)"
>>> and we'd cut out all the NSM bits before passing it on to GnuTLS. If
>>> there's nothing in the priority string, we'd look at
>>> `network-security-level', that would be the out-of-the-box use case.
>> 
>> I'm not sure we need to allow this to be customised at this fine-grained
>> level.  Does Firefox allow that, for instance?

RS> At least there's security.tls.version.min,
RS> security.ssl3.ecdhe_ecdsa_rc4_128_sha, and several other security.*
RS> prefs.  Dunno how these relate to Ted's suggestion.

I think most of those can be specified with the GnuTLS priority string,
but it's somewhat obscure how to do it. The GnuTLS guys suggested we
link the `network-security-level' or another variable to some default
priority string combinations, following at least the pattern of
https://github.com/nmav/fedora-crypto-policies/tree/master/profiles

Thread reference:
http://thread.gmane.org/gmane.network.gnutls.general/3695/focus=3696

If anyone is interested in providing a patch, feel free.  My suggestion
would be to provide some customize defaults for `gnutls-priority-string'
that are tagged helpfully and maybe even make them symbols (so the
translation to actual priority string happens under the covers).

Ted




  reply	other threads:[~2014-12-20 11:27 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-05 15:10 Additional network security Lars Magne Ingebrigtsen
2014-12-05 18:43 ` Stefan Monnier
2014-12-06 17:32   ` Lars Magne Ingebrigtsen
2014-12-06 22:51     ` Stefan Monnier
2014-12-07  5:35       ` Stephen J. Turnbull
2014-12-07 16:32         ` Ted Zlatanov
2014-12-07 16:41           ` Lars Magne Ingebrigtsen
2014-12-07 17:03             ` Ted Zlatanov
2014-12-07 17:45               ` Lars Magne Ingebrigtsen
2014-12-07 18:28                 ` Ted Zlatanov
2014-12-07 20:37                 ` chad
2014-12-18 21:54                 ` Reiner Steib
2014-12-20 11:27                   ` Ted Zlatanov [this message]
2014-12-08  1:44           ` Stephen J. Turnbull
2014-12-08  0:24         ` Richard Stallman
2014-12-08 14:04           ` Ted Zlatanov
2014-12-08 18:04             ` Lars Magne Ingebrigtsen
2014-12-08 20:48             ` Lars Magne Ingebrigtsen
2014-12-08 20:57               ` Lars Magne Ingebrigtsen
2014-12-08 21:26                 ` Lars Magne Ingebrigtsen
2014-12-05 20:02 ` Jens Lechtenboerger
2014-12-06 17:33   ` Lars Magne Ingebrigtsen
2014-12-10 16:01     ` Ted Zlatanov
2014-12-07 16:33 ` Ted Zlatanov
2014-12-07 16:47   ` 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=87tx0qsgrm.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).