On Mon 2019-05-13 01:01:57 +0100, Toni Mueller wrote:
> I did not do this. This variable is unset in my environment.
right, you were working with a pre-existing keyring. I believe that
keyring already had a copy of the teabot public key.
> Your experiment only shows that the key did *not* end
>
Hi Daniel,
On Sun, May 12, 2019 at 06:52:17PM -0400, Daniel Kahn Gillmor wrote:
> I'm not sure that this demonstrates what you're describing.
>
> Here is a run with gpg 2.2.15-1 that demonstrates the key being fetched
> into the extra keyring:
>
> 0 dkg@alice:/tmp/cdtemp.AhkyjS$ export
Control: tags 928894 + moreinfo
Hi Toni--
On Sun 2019-05-12 19:46:45 +0100, Toni wrote:
> --recv-keys does not seem to honour the keyring options, so the received
> key ends up in the wrong keyring:
>
> $ touch ~/mnt/tools/gitea-keys.gpg
> $ gpg --no-default-keyring --keyring
Package: gpg
Version: 2.2.12-1
Severity: normal
Hi,
--recv-keys does not seem to honour the keyring options, so the received
key ends up in the wrong keyring:
$ touch ~/mnt/tools/gitea-keys.gpg
$ gpg --no-default-keyring --keyring ~/mnt/tools/gitea-keys.gpg --recv-keys
4 matches
Mail list logo
