--===============2110540649==
Content-Type: multipart/alternative; boundary=94eb2c0b66e63d77fb05313e38ec

--94eb2c0b66e63d77fb05313e38ec
Content-Type: text/plain; charset=UTF-8

On Sun, Apr 24, 2016 at 6:51 PM, Daniel H. Werner <daniel@hillsdalecorp.com>
wrote:
>
> 4) My existing keys were created (in 2009 in PGP) at 2048 length.  Should
> I change them to 4096?  If so, how?
>

I think that 2048 is still OK.
But if you decide to upgrade, you can find some good advice here:
https://johnlane.ie/i-have-a-new-gnupg-key.html

--94eb2c0b66e63d77fb05313e38ec
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On S=
un, Apr 24, 2016 at 6:51 PM, Daniel H. Werner <span dir=3D"ltr">&lt;<a href=
=3D"mailto:daniel@hillsdalecorp.com" target=3D"_blank">daniel@hillsdalecorp=
.com</a>&gt;</span> wrote:<blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204)=
;border-left-style:solid;padding-left:1ex"><div style=3D"word-wrap:break-wo=
rd"><div>4) My existing keys were created (in 2009 in PGP) at 2048 length.=
=C2=A0 Should I change them to 4096?=C2=A0 If so, how?<br></div></div></blo=
ckquote><div><br></div><div>I think that 2048 is still OK.</div><div>But if=
 you decide to upgrade, you can find some good advice here:</div><div><a hr=
ef=3D"https://johnlane.ie/i-have-a-new-gnupg-key.html">https://johnlane.ie/=
i-have-a-new-gnupg-key.html</a></div><div>=C2=A0</div></div></div></div>

--94eb2c0b66e63d77fb05313e38ec--


--===============2110540649==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

--===============2110540649==--