From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: Network Security Manager merge time?
Date: Tue, 25 Nov 2014 09:20:39 -0500 [thread overview]
Message-ID: <871torfjk8.fsf@lifelogs.com> (raw)
In-Reply-To: m3389cbxli.fsf@stories.gnus.org
On Fri, 21 Nov 2014 12:29:45 +0100 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
LMI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> Looking at the code, there's a lot of copy+pasta there between the
>> GnuTLS verification in `gnutls-boot' and the message collection in
>> `gnutls-peer-status'. Could you factor that out so there's only one
>> sequence of checks to maintain, especially since I'd like to deprecate
>> the GnuTLS verification in favor of NSM? Basically call
>> `gnutls-peer-status' in `gnutls-boot' and then iterate through the
>> messages (which can be the simpler version you use instead of the one
>> with the hostname attached I have in `gnutls-boot'). I can do it if you
>> prefer.
LMI> Sure; go ahead. The verification checks should probably be factored out
LMI> from `gnutls-peer-status', though, since `gnutls-boot' doesn't need the
LMI> other things it calculates (like the fingerprints etc).
OK, done as follows:
* `gnutls-peer-status' returns a simple list of symbols, which can then
be passed to `gnutls-peer-status-warning-describe' for the full
string. That could turn into a more complex struct or symbol
properties, but for now it's just a string message. I adapted
`gnutls-boot' accordingly. The certificate info is not generated when
it's called through `gnutls-boot' because that struct is not populated
yet, so there's no wasted cycles.
* nsm.el was also adapted accordingly.
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)
* add the ability to set the `network-security-level' per hostname regex
* put the 'gnutls customization group next to 'nsm under 'comm
WDYT?
Ted
next prev parent reply other threads:[~2014-11-25 14:20 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 [this message]
2014-11-25 16:30 ` Lars Magne Ingebrigtsen
2014-11-25 16:46 ` Ted Zlatanov
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
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=871torfjk8.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).