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: NSM certificate prompt
Date: Sat, 13 Dec 2014 15:02:48 -0500	[thread overview]
Message-ID: <87mw6rz5av.fsf@lifelogs.com> (raw)
In-Reply-To: 87egs3e4xd.fsf@gmx.de

On Sat, 13 Dec 2014 20:16:30 +0100 Michael Albinus <michael.albinus@gmx.de> wrote: 

MA> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>> Eli Zaretskii <eliz@gnu.org> writes:
>> 
>>> A middle ground would be to offer to perform an update of the
>>> certificates when validation fails.
>> 
>> Yes, that would be nice.  We'd have to have a secure way to retrieve
>> those certificates, though.  Perhaps we could use GNU ELPA for this?
>> Wasn't there some work done on signing packages?

We have signed packages (but you need GnuPG installed).

The last time I brought up storing the CA certificates inside Emacs,
there was no interest in maintaining that facility. Similarly, we don't
package GnuTLS with Emacs, so the user has to update it manually (we
also discussed this with Eli a while back).

MA> That's not the crucial point. A root certificate could be compromised,
MA> and with this compromised root certificate a validation might still
MA> succeed when it shouldn't. ELPA does not has the means to urge a package
MA> update of the hypothetical ca-certificates package, when a new version
MA> appears.

Well, typically CRLs are used for such urgent revocations, right? So
those could be supported specifically. And we could say that
`network-security-level' of 'high or above requires having the latest
GNU ELPA certificates package. I think it's technically possible.

MA> I don't believe this belongs to Emacs' core functionality. It might be
MA> better to investigate first, whether there exist already an
MA> infrastructure on the different supported systems we could use. Like the
MA> Debian package I've mentioned already.

It's definitely easier to rely on the host OS.  I don't know if it's
always the right thing because not all platforms are up to date, and the
user may not be able to control the CA store updates.  The GnuTLS
updates are handled similarly.

Ted




  reply	other threads:[~2014-12-13 20:02 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-13 14:43 NSM certificate prompt Eli Zaretskii
2014-12-13 15:12 ` Lars Magne Ingebrigtsen
2014-12-13 16:01   ` Eli Zaretskii
2014-12-13 16:04     ` Lars Magne Ingebrigtsen
2014-12-13 16:46       ` Eli Zaretskii
2014-12-13 17:27         ` Lars Magne Ingebrigtsen
2014-12-13 15:27 ` Michael Albinus
2014-12-13 15:35   ` Lars Magne Ingebrigtsen
2014-12-13 16:57     ` Michael Albinus
2014-12-13 17:06       ` Eli Zaretskii
2014-12-13 17:29       ` Lars Magne Ingebrigtsen
2014-12-13 18:03         ` Eli Zaretskii
2014-12-13 18:06           ` Lars Magne Ingebrigtsen
2014-12-13 19:16             ` Michael Albinus
2014-12-13 20:02               ` Ted Zlatanov [this message]
2014-12-13 16:03   ` Eli Zaretskii
2014-12-13 16:39   ` Eli Zaretskii
2014-12-13 17:06     ` Michael Albinus
2014-12-13 18:01       ` Eli Zaretskii
2014-12-13 19:09         ` Michael Albinus
2014-12-13 19:13         ` Eli Zaretskii
2014-12-13 19:47           ` Ted Zlatanov
2014-12-13 20:06             ` Eli Zaretskii
2014-12-14  0:23               ` Lars Magne Ingebrigtsen
2014-12-14  1:38               ` Ted Zlatanov
2014-12-14  3:46                 ` Eli Zaretskii
2014-12-14  8:16                   ` Lars Magne Ingebrigtsen
2014-12-14 16:04                     ` Eli Zaretskii
2014-12-19 12:14                       ` Lars Ingebrigtsen
2014-12-19 14:41                         ` Eli Zaretskii
2014-12-19 16:42                           ` Ivan Shmakov
2014-12-19 16:47                           ` Lars Ingebrigtsen
2014-12-19 19:53                         ` Simon Leinen
2014-12-19 21:37                           ` Eli Zaretskii
2014-12-14 11:34                   ` Ted Zlatanov
2014-12-14 12:52                     ` Michael Albinus
2014-12-14 16:53                     ` Eli Zaretskii

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