From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Kelly Dean <kelly@prtime.org>
Cc: emacs-devel@gnu.org
Subject: Re: Whose keys go on elpa/gnupg/pubring.gpg?
Date: Thu, 08 Jan 2015 00:01:25 -0500 [thread overview]
Message-ID: <jwviogh7tpf.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <pQmJ4gMCcZWumeq83WekcrawzLFpOMWwnyh0QMo6hjf@local> (Kelly Dean's message of "Thu, 08 Jan 2015 03:36:40 +0000")
> In that case, where do individual package maintainers' keys go?
Nowhere: the signatures only certify that this is the file that was
created on elpa.gnu.org. Adding package maintainer's signatures would
be a very different enterprise, which we haven't attacked (yet?).
Stefan
next prev parent reply other threads:[~2015-01-08 5:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 3:36 Whose keys go on elpa/gnupg/pubring.gpg? Kelly Dean
2015-01-08 5:01 ` Stefan Monnier [this message]
2015-01-08 6:40 ` Kelly Dean
2015-01-08 14:20 ` Stefan Monnier
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=jwviogh7tpf.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=kelly@prtime.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).