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: [PATCH] package.el: check tarball signature
Date: Sat, 05 Oct 2013 06:11:51 -0400	[thread overview]
Message-ID: <8738ogrpqw.fsf@flea.lifelogs.com> (raw)
In-Reply-To: 83mwmob3dm.fsf@gnu.org

On Sat, 05 Oct 2013 10:09:25 +0300 Eli Zaretskii <eliz@gnu.org> wrote: 

>> From: Ted Zlatanov <tzz@lifelogs.com>
>> Date: Fri, 04 Oct 2013 17:14:44 -0400
>> 
>> >> Actually, let's wait.  If all turn out well, most/all ELPA archives will
>> >> start providing signatures in the not too distant future and there'll be
>> >> no need for per-archive settings (and we can change the default to t).
>> 
EZ> Are you saying that verification will not need gpg be installed?
>> 
>> If my work with libnettle progresses well, I think we'll be able to at
>> least verify GPG signatures without calling out to GnuPG or other tools
>> on all the platforms that have libnettle+libhogweed (any platforms with
>> GnuTLS support AFAIK).

EZ> And what about users whose Emacs doesn't have GnuTLS?  Are we saying
EZ> they will not be able to install packages from ELPA without being
EZ> annoyed by prompts and error messages?

No one has said that AFAIK.

My suggestion was to give users the choice (per archive) to always,
maybe, or never verify packages.  Currently this choice is global in
Daiki Ueno's changes that were committed recently, but it's still a
choice.

The signature verification method will be anything that can take a .sig
file and check that it's been signed by a maintainer's key, according to
the OpenPGP protocol in RFC 4880.  Daiki Ueno has implemented a
epg.el-backed verification method using calls to the external GnuPG that
works today.  I will (perhaps with others' help) try to implement a
libnettle+libhogweed-backed verification method that only requires those
libraries and makes no external calls.  I expect the user will be able
to decide which one to use, or even both if they wish.

Ted




  reply	other threads:[~2013-10-05 10:11 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-30 19:48 [PATCH] package.el: check tarball signature Daiki Ueno
2013-09-30 19:58 ` Eli Zaretskii
2013-10-02  6:20   ` [PATCHv2] " Daiki Ueno
2013-10-02 10:43     ` Ted Zlatanov
2013-09-30 21:54 ` [PATCH] " Ted Zlatanov
2013-09-30 22:56   ` Stefan Monnier
2013-10-02 11:17     ` Ted Zlatanov
2013-10-02  7:16   ` Daiki Ueno
2013-10-02 10:41     ` Ted Zlatanov
2013-10-02 12:22       ` Daiki Ueno
2013-10-02 13:53         ` Ted Zlatanov
2013-10-03  3:51           ` Stefan Monnier
2013-10-02 13:15     ` Thien-Thi Nguyen
2013-10-03  3:45       ` Stefan Monnier
2013-10-03  3:52     ` Stefan Monnier
2013-10-03  7:18       ` Daiki Ueno
2013-10-03 14:19         ` Ted Zlatanov
2013-10-03 15:01           ` Stefan Monnier
2013-10-04 19:23             ` Eli Zaretskii
2013-10-04 21:14               ` Ted Zlatanov
2013-10-05  0:34                 ` Daiki Ueno
2013-10-05  5:40                   ` Stephen J. Turnbull
2013-10-05 10:03                     ` Ted Zlatanov
2013-10-05 15:07                       ` Stephen J. Turnbull
2013-10-05 21:51                         ` Ted Zlatanov
2013-10-05  9:57                   ` Ted Zlatanov
2013-10-05  7:09                 ` Eli Zaretskii
2013-10-05 10:11                   ` Ted Zlatanov [this message]
2013-10-05 12:37                     ` Eli Zaretskii
2013-10-05 13:53                       ` Stefan Monnier
2013-10-04  2:46           ` Daiki Ueno
2013-10-04 16:19             ` Ted Zlatanov

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=8738ogrpqw.fsf@flea.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.