> The problem is that a private key protected by a weak cipher is still
> potentially compromised if an attacker can get any copy of the key prior
> to migrating it to a stronger cipher. In other words, if an attacker is
> able to obtain your current key blob, the attacker can still compromise
>
> Sent: Tuesday, March 23, 2021 at 9:44 AM
> From: "Ingo Klöcker"
>
> It's defined in the separate libgpg-error library. It corresponds to the
> symbol GPG_ERR_WEAK_KEY. This symbol occurs in libgcrypt (the low-level
> crypto
> library of GnuPG), e.g. in blowfish.c, and in gnupg.
>
Okay, I
> > I try to import this key manually (--import), gpg throws a "weak
> > encryption key" error and refuses to import it. ...which I find
>
> Can you please paste the exact error message and the output of
> "gpgconf --show-versions"?
>
>
> Shalom-Salam,
>
>Werner
>
Sure. My gpgconf doesn't
Hello all,
I have a private key protected by blowfish cipher that despite a random salt
and several rounds of RIPEMD160 iterations is still considered "weak" by GnuPG
and it refuses to do anything with it. When I try to import this key manually
(--import), gpg throws a "weak encryption key"
Hello, thank you for your response.
> Sent: Saturday, February 27, 2021 at 10:56 AM
> From: "Werner Koch"
> To: "jsmith9810--- via Gnupg-users"
> Cc: jsmith9...@gmx.com
> Subject: Re: New packet format for OpenPGP
>
> On Fri, 26 Feb 2021 20:14, jsmit
Hello,
I noticed that GnuPG (I'm using v2.2.19) still uses the old format OpenPGP
packets, when I export my keys, for example.
Is there a way I can make it use the new format instead (and possibly make it
default)?
It does understand the new format, I just can't seem to find the option to
On 4/10/21, 10:18 PM "Ángel" wrote:
>
> On 2021-04-10 at 04:08 +, Kiara Stankovic wrote:
> >
> > Adding a subkey with keygrip also doesnt work, since the new subkey
> > has a different keyid than the original key.
>
> The solution of https://security.stackexchange.com/a/160847/ should
>
