From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Daiki Ueno <ueno@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] package.el: check tarball signature
Date: Sat, 05 Oct 2013 14:40:46 +0900 [thread overview]
Message-ID: <87zjqol1gh.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <8761tcpnbn.fsf-ueno@gnu.org>
Daiki Ueno writes:
> Ted Zlatanov <tzz@lifelogs.com> writes:
>
> > I can put up my current patch for review but I still have HMAC, maybe
> > UMAC, and RSA+DSA+ECC crypto to finish. The hashing methods and the
> > ciphers in ECB, CBC, and CTR modes are done with tests. Should I make a
> > Bazaar branch for that work? Is anyone interested in reviewing it?
>
> Probably I should shut up, but...
Please don't. You seem to be the only sane voice[1] in the crowd.
Not that I agree 100% with everything you've written, but at least you
have the security mindset. Everybody else seems to think this is like
fixing any other bug.
> Does that mean all the package signatures will be signed/verified with
> your own "Emacs internal" signature format, and all the packagers will
> need to use your tool and Emacs, instead of GPG, right?
He has suggested that, but AFAIK he doesn't insist on it.
Still, the whole idea worries me; there's no reason to suppose it will
increase security, and Ted never has seemed to grasp that security is
not a SMOP, nor that security is inherently inconvenient. Quis
custodiat ipsos custodes? Do you really want to put a possible fox in
charge of the security check at the henhouse door?
> That is what I opposed again and again and suggested to use a standard
> format.
+1
Footnotes:
[1] I don't understand security well enough to claim to be a sane
voice, but at least I know how little I know.
next prev parent reply other threads:[~2013-10-05 5:40 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 [this message]
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
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=87zjqol1gh.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=emacs-devel@gnu.org \
--cc=ueno@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.