From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: convenient digital signing for el files and snippets
Date: Wed, 09 Mar 2011 11:43:55 -0600 [thread overview]
Message-ID: <8739mwp4tg.fsf@lifelogs.com> (raw)
In-Reply-To: 87bp1k2ra5.fsf@geneva.hpsy.me
On Wed, 09 Mar 2011 10:27:14 -0600 Joseph Gay <gilleylen@gmail.com> wrote:
>> - older and legacy code doesn't have to be modified to be signed
JG> This wouldn't affect unsigned code. It would be treated the same as it
JG> is now. Only for things that are signed would there be any potential
JG> benefit (assurance that the signature is trusted and validated).
Right. So what could make the hundreds of EmacsWiki contributors add
this extra code to their source? And what benefit is it to the end
user? EmacsWiki is already open to editing, so what prevents an
uploader from signing malicious code?
JG> I have some working code now, so I will look into what it would take to
JG> implement a mechanism for ELPA, assuming that's not already in the
JG> works.
I'm not aware of it; the TODO list is at the beginning of package.el.
If you write this I'll be glad to test it.
Ted
prev parent reply other threads:[~2011-03-09 17:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 6:12 convenient digital signing for el files and snippets Joseph Gay
2011-03-09 15:33 ` Ted Zlatanov
2011-03-09 16:27 ` Joseph Gay
2011-03-09 17:43 ` Ted Zlatanov [this message]
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=8739mwp4tg.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).