On January 24, 2018 11:58 PM, Werner Koch wrote:
>On Tue, 23 Jan 2018 08:41, gnupg-users@gnupg.org said:
>
>>I would like to clean the key of the spam signatures while preserving
>> any signatures made by Alice (or anyone else I have trusted on my
>> keyring). Does there exist a command/option to
On Thu, 25 Jan 2018 09:39, g...@unixarea.de said:
> $ ssh some-host
>
> fails to ask for the PIN.
That is because ssh has no mechanism to tell the ssh-agent (in this case
gpg-agent) the DISPLAY or tty to use for pinentry. This the pinentry
pops up on the tty or X server gpg-agent was initially s
Hello,
A bit triggered by the last thread "Why exactly does pinentry fails with
gpg-agent and ssh support?" I want to report a similar issue which I do not
understand.
I have the 'pinentry' in /usr/local/bin/pinentry as a sym-link to the qt5
version:
$ ls -l /usr/local/bin/pinentry
lrwxr-xr-x
On Thu, 25 Jan 2018 05:43, gnupg-users@gnupg.org said:
> After looking at the content of subpacket 33, it appears to be the
> signing-key's fingerprint prepended by '0x04'.
>
> So I'm guessing subpacket 33 is to be a more robust version of subpacket 16
> (Issuer)?
Right. From RFC-4880bis (draft
On Tue, 23 Jan 2018 08:41, gnupg-users@gnupg.org said:
> I would like to clean the key of the spam signatures while preserving
> any signatures made by Alice (or anyone else I have trusted on my
> keyring). Does there exist a command/option to accomplish this in
> gpg2?
I do blacklisting of certa
