Using ELG sign and encrypt key

[David T-G]

--kUmo4NyTJbuJZ752
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

David, et al --

=2E..and then David Pic?n ?lvarez said...
%=20
% At the risk of seeming stubborn:

*grin*


%=20
% > > When I created my new gpg key, I decided to use ElGamal sign and encr=
ypt
% > > key, because it permits having a 4096 signature key, and I thought th=
at
=2E..
% > They won't work with PGP, signing is very slow and there are probably
=2E..
% 2) On slowness, since I use signing interactively, it doesn't seem to be =
an
% issue right now. I don't notice the slowness, to tell the truth.

I used to have a 4k key but didn't do it again when creating my current
key because I did.  It wasn't so slow to sign, but it was a pig to
verify.  Your messages are the same; it takes mutt about seven seconds to
open and verify one of your messages, while it takes just under a second
(as well as I can tell) to open, say, mine with my current key.  Have you
tried reading your own messages to see how your performance looks?

I wasn't as much worried about my correspondents (since I'm on a box with
two Celeron-400s, many folks had beefier hardware than I, and besides
they're not at my keyboard tapping their feet :-) but really didn't like
reading my own messages, so I went back to a 2k key for this round.


HTH & HAND (& if you create a new key I won't complain ;-)

:-D
--=20
David T-G                      * It's easier to fight for one's principles
(play) davidtg@justpickone.org * than to live up to them. -- fortune cookie
(work) davidtgwork@justpickone.org
http://www.justpickone.org/davidtg/    Shpx gur Pbzzhavpngvbaf Qrprapl Npg!


--kUmo4NyTJbuJZ752
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9ALh6Gb7uCXufRwARAjPyAKCDXmsFUSrHLltPP0VA/NCZHTeiPgCfYz+P
tYPL/Av23R/Xw2wck/j1bRI=
=/lIZ
-----END PGP SIGNATURE-----

--kUmo4NyTJbuJZ752--