public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kristian Fiskerstrand <k_f@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] can't gpg sign with repoman, but can with git
Date: Thu, 20 Jul 2017 13:23:14 +0200	[thread overview]
Message-ID: <089c653e-a7a5-b632-ec80-c587a62c0cdc@gentoo.org> (raw)
In-Reply-To: <91c6cc7d-2e03-4dc9-0c58-c63d049d13d0@gentoo.org>


[-- Attachment #1.1: Type: text/plain, Size: 932 bytes --]

On 07/20/2017 10:16 AM, Kristian Fiskerstrand wrote:
> What I have noticed with regards to git though, but not had time to
> debug is that it seems to do something odd with regards to communicating
> with the agent to begin with, and possibly spawns an own agent, at least
> sufficiently confusing that for smartcard use it fail to access the card
> due to locking and needing to re-insert the card.. with similar
> mechanism to use it outside of git context again afterwards.

And looking into this, the issue is actually a lack of sanitation of the
--homedir parameter for gpg-agent, so "$HOME/.gnupg" and "$HOME/.gnupg/"
is treated as separate directories and as such two separate agents are
started... reported upstream... will be nice to get rid of _that_ annoyance.

-- 
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2017-07-20 11:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-19 19:24 [gentoo-dev] can't gpg sign with repoman, but can with git Paweł Hajdan, Jr.
2017-07-19 19:43 ` Andrew Savchenko
2017-07-19 19:57   ` Joshua Kinard
2017-07-19 21:44     ` Mart Raudsepp
2017-07-20  5:49       ` Andrew Savchenko
2017-07-20  8:16         ` Kristian Fiskerstrand
2017-07-20 11:23           ` Kristian Fiskerstrand [this message]
2017-07-20  9:38 ` Kristian Fiskerstrand
2017-08-03  9:07   ` Paweł Hajdan, Jr.

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=089c653e-a7a5-b632-ec80-c587a62c0cdc@gentoo.org \
    --to=k_f@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