Daniel Colquitt via Gnupg-users wrote:
Whilst AES128 is probably okay for now, SHA1 has been broken for well over 15
years.
Has it really been that long? ... No, it has not been: a free-start
collision was found on the SHA-1 compression function in 2015, less than
7 years ago.
As far as I
> On 19 Feb 2022, at 14:52, Werner Koch wrote:
>
> gpg does not encrypt private keys. This is done by gpg-agent. The
> method how the keys are protected internally are out of scope for
> OpenPGP. See gnupg/agent/keyformat.txt for the specification of the
> internal format.
Apologies for con
On Fri, 18 Feb 2022 13:08, Daniel Colquitt said:
> Is the suggestion the gpg does not respect these flags when applying
> symmetric encryption to keys?
gpg does not encrypt private keys. This is done by gpg-agent. The
method how the keys are protected internally are out of scope for
OpenPGP. S
Hi Vedaal,
> Try this:
> In gpg.conf file add the option of
> --expert
> and in personal preferences, list only AES 256,
> Not the other strengths.
> Keep all of the s2k options you listed, and try generating a new key again
> Vedaal
Many thanks for the suggestion, but I’m afraid that this stil
