all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: Network Security Manager merge time?
Date: Tue, 25 Nov 2014 11:46:52 -0500	[thread overview]
Message-ID: <87sih7cjnn.fsf@lifelogs.com> (raw)
In-Reply-To: m3fvd78cpf.fsf@stories.gnus.org

On Tue, 25 Nov 2014 17:30:36 +0100 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote: 

LMI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> I think we should now do the following:
>> 
>> * deprecate `gnutls-verify-error' in favor of `network-security-level'
>> 
>> * to help the migration, map :trustfiles and :hostname to 'medium (IIUC)

LMI> I think that proper Professional Security Professionals won't trust that
LMI> us lowly Emacs developers can get something as sacred as this stuff
LMI> right, so they will still want to be able to instruct the gnutls library
LMI> to refuse connections directly.

But it will!  It will simply look at `network-security-level' instead of
the old variable.

>> * add the ability to set the `network-security-level' per hostname regex

LMI> I still don't see the use case.  :-) The only reason to bump the level
LMI> over `medium' is that the user is worried that the NSA is paying a rogue
LMI> CA to issue certificates for your bank, and if you are, you should be
LMI> running on `high' always.

OK, you may be right.  No need to overengineer it.

LMI> And `medium' is so unintrusive that I hope that nobody will feel the
LMI> need to run with `low'.  If they feel that need, then we've misdesigned
LMI> something.

Such an optimist, you are.

>> * put the 'gnutls customization group next to 'nsm under 'comm

LMI> Yeah, that would be nice.

Moved.

Ted




  reply	other threads:[~2014-11-25 16:46 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-19 16:22 Network Security Manager merge time? Lars Magne Ingebrigtsen
2014-11-19 16:40 ` Ted Zlatanov
2014-11-19 16:53   ` Lars Magne Ingebrigtsen
2014-11-19 17:30     ` Ted Zlatanov
2014-11-19 17:59       ` Lars Magne Ingebrigtsen
2014-11-19 18:34         ` Ted Zlatanov
2014-11-19 20:00           ` Ivan Shmakov
2014-11-19 20:25             ` Ted Zlatanov
2014-11-19 21:41           ` Ted Zlatanov
2014-11-21 11:29             ` Lars Magne Ingebrigtsen
2014-11-25 14:20               ` Ted Zlatanov
2014-11-25 16:30                 ` Lars Magne Ingebrigtsen
2014-11-25 16:46                   ` Ted Zlatanov [this message]
2014-11-25 17:08                     ` Lars Magne Ingebrigtsen
2014-11-25 18:20                       ` intrusive changes Ivan Shmakov
2014-11-30 13:51                         ` Stefan Monnier
2014-11-30 15:12                           ` Ivan Shmakov
2014-11-30 18:07                             ` Stefan Monnier
2014-12-02 10:03                               ` Ivan Shmakov
2014-12-02 13:50                                 ` Stefan Monnier
2014-11-19 18:22   ` Network Security Manager merge time? Lars Magne Ingebrigtsen
2014-11-19 20:46     ` Eli Zaretskii
2014-11-19 20:54       ` Lars Magne Ingebrigtsen
2014-11-19 20:58         ` Lars Magne Ingebrigtsen
2014-11-19 21:18         ` Eli Zaretskii
2014-11-20  8:42           ` Lars Magne Ingebrigtsen
2014-11-20 16:16             ` Eli Zaretskii
2014-11-19 17:28 ` Robert Pluim
2014-11-19 17:50   ` Lars Magne Ingebrigtsen
2014-11-19 19:51     ` Robert Pluim
2014-11-19 19:56       ` Lars Magne Ingebrigtsen
2014-11-19 20:06         ` Robert Pluim
2014-11-19 20:20           ` Lars Magne Ingebrigtsen
2014-11-19 20:25             ` Lars Magne Ingebrigtsen
2014-11-19 20:26             ` Robert Pluim
2014-11-19 20:32               ` Lars Magne Ingebrigtsen
2014-11-20  8:00                 ` Robert Pluim
2014-11-20  8:43                   ` Lars Magne Ingebrigtsen
2014-11-20  9:04           ` Robert Pluim
2014-11-20 10:39             ` Lars Magne Ingebrigtsen
2014-11-20 11:34               ` Robert Pluim

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=87sih7cjnn.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 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.