From: Michael Weber <xmw@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] repoman commit unexpectedly drops FEATURES="sign" on error
Date: Thu, 20 Jun 2013 08:39:50 +0200 [thread overview]
Message-ID: <51C2A3B6.2000506@gentoo.org> (raw)
In-Reply-To: <51C27699.8090600@gentoo.org>
On 06/20/2013 05:27 AM, Zac Medico wrote:
> On 06/19/2013 08:25 PM, Zac Medico wrote:
>> On 06/19/2013 07:59 PM, "Paweł Hajdan, Jr." wrote:
>>> I was surprised by repoman just dropping FEATURES="sign" . I'm aware
>>> that at that time it has to commit an updated Manifest to prevent
>>> breakages, so if gpg fails it proceeds, but is there something it could
>>> do to check gpg sanity before committing anything?
Failing at the password prompt (two chances on regular pinentry) also
results in this behaviour.
>> It seems the simplest way to go would be to do a test signature before
>> commit, as suggested here:
>>
>> https://bugs.gentoo.org/show_bug.cgi?id=298605
>>
>> Is it okay to assume that everyone uses gpg-agent, so they won't have to
>> enter the passphrase more than once?
I have a remote (ssh) test-box to work on the tree, I don't want to
cache my decrypted key there.
Having the crypted version there is bad enough, but GPG_AGENT protocol
only exchanges passwords (unlike SSH_AGENT). GPG_AGENT forwarding over
SSH can be done with a general unix domain socket forwading hack [1].
> Or, we could skip the test signature if the GPG_AGENT_INFO variable is
> not set?
It's a clue, but the key-cache can be expired and a bad password entry
can still result in failure.
[1] http://25thandclement.com/~william/projects/streamlocal.html
--
Michael Weber
Gentoo Developer
web: https://xmw.de/
mailto: Michael Weber <xmw@gentoo.org>
next prev parent reply other threads:[~2013-06-20 6:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 2:59 [gentoo-dev] repoman commit unexpectedly drops FEATURES="sign" on error "Paweł Hajdan, Jr."
2013-06-20 3:25 ` Zac Medico
2013-06-20 3:27 ` Zac Medico
2013-06-20 6:39 ` Michael Weber [this message]
2013-06-20 9:16 ` Michał Górny
2013-06-23 0:02 ` "Paweł Hajdan, Jr."
2013-06-23 8:19 ` Michał Górny
2013-06-23 21:06 ` Zac Medico
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=51C2A3B6.2000506@gentoo.org \
--to=xmw@gentoo.org \
--cc=gentoo-dev@lists.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