From: "Robin H. Johnson" <robbat2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: zmedico@gentoo.org
Subject: Re: [gentoo-dev] RFC: Gentoo GPG key policies
Date: Fri, 15 Mar 2013 01:01:18 +0000 [thread overview]
Message-ID: <robbat2-20130315T005848-062500060Z@orbis-terrarum.net> (raw)
In-Reply-To: <20130314171415.525323a2@pomiocik.lan>
On Thu, Mar 14, 2013 at 05:14:15PM +0100, Michał Górny wrote:
> If that means doing an additional signature every time something is
> going to be committed, that sounds like an overkill. If we were to do
> something radical, I'd rather be in favor of disabling keyword
> expansion completely and finally being able to do sane commits.
I foresee it as more of:
IFF this commit will call GPG later, ensure the agent can access the
secret key BEFORE trying to sign at the end.
As to how to accomplish this, it's either a throwaway sig, or poking the
agent protocol directly.
--
Robin Hugh Johnson
Gentoo Linux: Developer, Trustee & Infrastructure Lead
E-Mail : robbat2@gentoo.org
GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85
next prev parent reply other threads:[~2013-03-15 1:01 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 23:27 [gentoo-dev] RFC: Gentoo GPG key policies Robin H. Johnson
2013-02-18 23:41 ` Robin H. Johnson
2013-02-19 3:36 ` Kent Fredric
2013-02-19 4:09 ` Robin H. Johnson
2013-02-19 4:46 ` Brian Dolbec
2013-02-19 7:38 ` Kent Fredric
2013-02-19 15:52 ` Alec Warner
2013-02-19 4:25 ` [gentoo-dev] " Ryan Hill
2013-02-19 6:51 ` [gentoo-dev] " Eray Aslan
2013-02-20 0:34 ` Stefan Behte
2013-02-20 3:12 ` Robin H. Johnson
2013-02-20 6:32 ` Alec Warner
2013-02-20 17:05 ` Robin H. Johnson
2013-02-20 18:41 ` James Cloos
2013-02-20 19:36 ` Robin H. Johnson
2013-02-20 20:22 ` Andreas K. Huettel
2013-02-20 21:31 ` Robin H. Johnson
2013-02-20 20:38 ` Luis Ressel
2013-02-20 21:37 ` Robin H. Johnson
2013-02-20 21:55 ` Luis Ressel
2013-02-21 9:09 ` Michał Górny
2013-02-21 9:41 ` Markos Chandras
2013-02-26 10:10 ` grozin
2013-02-27 15:12 ` Luis Ressel
2013-02-27 19:04 ` Robin H. Johnson
2013-02-27 20:27 ` Alec Warner
2013-03-14 3:50 ` grozin
2013-03-14 7:19 ` justin
2013-03-14 9:12 ` Robin H. Johnson
2013-03-14 15:26 ` Zac Medico
2013-03-14 16:14 ` Michał Górny
2013-03-14 16:30 ` Zac Medico
2013-03-15 0:58 ` Robin H. Johnson
2013-03-15 1:01 ` Robin H. Johnson [this message]
2013-03-15 2:32 ` Michael Mol
2013-03-15 3:18 ` Robin H. Johnson
2013-03-15 3:33 ` Michael Mol
2013-03-15 5:12 ` Robin H. Johnson
2013-03-15 4:44 ` Michał Górny
2013-03-15 5:01 ` Robin H. Johnson
2013-03-22 6:37 ` grozin
2013-03-22 8:36 ` Panagiotis Christopoulos
2013-03-22 8:47 ` grozin
2013-03-22 14:19 ` David Abbott
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=robbat2-20130315T005848-062500060Z@orbis-terrarum.net \
--to=robbat2@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=zmedico@gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox