On 03/09/18 18:56, Fiedler Roman wrote:
> With gpg1 a similar command should have verified, that the signature
> is exactly from the single public key stored in "key.pub".
This has never been a supported use of gpg, it just happened to work
because GnuPG 1.4 happened to use a bunch of exported
Hello List,
Just for the records: a gnupg2 "ERROR key_generate 33554531" is fixed by
sending " %no-protection" via the command-fd. It seems that a password-less key
was generated with gpg1 just by not setting a password. With gnupg2 this
command is needed.
@Devs: It would be really nice to
As long as you did not publish reports revocation, delete the key and re-import
it without the revocation cert.
Am 3. September 2018 17:03:19 MESZ schrieb "Roland Siemons (P)"
:
>Dear GnuPG,
>
>I am already using GnuPG for a long time. But try to improve my
>understanding of and working with
Dear GnuPG,
I am already using GnuPG for a long time. But try to improve my
understanding of and working with it.
I became a member of Free Software Foundation Europe, and got a
smartcard. I wanted to use it.
And that is where the trouble started:
I intended to copy all my personal keys to the
Hi,
>> tested & confirmed with GnuPG 2.2.10, libgcrypt 1.8.3 Debian Stretch 9.5
>
> Not reproducible here (similar on Debian Stretch).
>
> I tested with no configuration.
>
> Is it reproducible under no configuration?
>
> I tested with:
>
> $ export GNUPGHOME=/tmp/g; mkdir -m=0700
On 08/29/2018 12:41 AM, Kristian Fiskerstrand wrote:
> On 08/28/2018 08:22 PM, Daniel Kahn Gillmor wrote:
>> On Sat 2018-08-25 08:18:48 +0200, sunri...@gmx.com wrote:
>>> Hi all, since some days I'm having an issue with pinentry, I've set the
>>> default agent as pinentry-qt4
>>> from
mlnl wrote:
>> gpg: signing failed: Invalid length
>> gpg: make_keysig_packet failed: Invalid length
>> Key generation failed: Invalid length
>
> tested & confirmed with GnuPG 2.2.10, libgcrypt 1.8.3 Debian Stretch 9.5
Not reproducible here (similar on Debian Stretch).
I tested with no
