<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"></div><div dir="ltr">Hi Vedaal,</div><div dir="ltr"><br><blockquote type="cite"><span style="font-family: Arial; font-size: 14px;">Try this:</span></blockquote><blockquote type="cite"><span style="font-family: Arial; font-size: 14px;">In gpg.conf file add the option of</span></blockquote><blockquote type="cite"><span style="font-family: Arial; font-size: 14px;">--expert</span></blockquote><blockquote type="cite"><span style="font-family: Arial; font-size: 14px;">and in personal preferences, list only AES 256,</span></blockquote><blockquote type="cite"><span style="font-family: Arial; font-size: 14px;">Not the other strengths. </span></blockquote><blockquote type="cite"><span style="font-family: Arial; font-size: 14px;">Keep all of the s2k options you listed, and try generating a new key again</span></blockquote><blockquote type="cite"><span style="font-family: Arial; font-size: 14px;">Vedaal </span></blockquote><br></div><div dir="ltr">Many thanks for the suggestion, but I’m afraid that this still does not work for me.</div><div dir="ltr"><br></div><div dir="ltr">It seems the gnupg ignores all s2k and cipher preference flags when encrypting private keys. If this is indeed the intended behaviour (although I have no idea why it should be), perhaps it would a good idea to add a warning to the man pages?</div><div dir="ltr"><br></div><div dir="ltr">Dan</div></body></html>