[Gpg4win-users-en] Changing the encryption algorithm used for PGP/GPG private key

[Bernhard Reiter]

Hi Daniel,

Am Samstag 12 Februar 2022 21:32:51 schrieb Daniel Colquitt:
> I've read various turorials and posts regarding changing the algorithm used
> to encrypt my private PGP keys. 

my guess is that the options change the behaviour of the internal storage
of private keys, but not the export behaviour. 
So you'd need to inspect the contents of $GNUPGHOME/private-keys-v1.d/
(use a text editor) and see of the options change something.

> However, nothing I have tried seems to 
> work. I am using gpg4win:

> s2k-mode 3
> s2k-cipher-algo AES256
> s2k-digest-algo SHA512
> s2k-count 65011712
> cipher-algo AES256

> gpg -vv --cipher-algo AES256 --export-secret-keys
> A7AA75FD6A11F453DE501E38D3E3B91787699C75 -a > key.txt

> gpg --list-packets key.txt

> :secret key packet:
>     iter+salt S2K, algo: 7, SHA1 protection, hash: 2,

> This would seem to suggest that the key is still encrypted using AES128
> (algo 7) and a SHA1 hash.

Take this question to the gnupg-users@ as it is platform independent
and thus on-topic there.

Best Regards,
Bernhard


-- 
www.intevation.de/~bernhard   +49 541 33 508 3-3
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.wald.intevation.org/pipermail/gpg4win-users-en/attachments/20220214/647c08b2/attachment.sig>