-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all.. I'm trying to get this to work. I've got a 1024k key working. But a few of my buddies are using 4096k keys. How can I work with this? Thanks JIM - -- Jim Hatridge Linux User #88484 - ------------------------------------------------------ BayerWulf Linux System # 129656 The Recycled Beowulf Project Looking for throw-away or obsolete computers and parts to recycle into a Linux super computer -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+iaDpv3Z9K7QSWt4RAjYsAKDV2YAG4qT4jnxk7DVdY6dYXqzhmQCfQXZD EThAKH5dFmrU2XqyJoCvcXI= =R1iR -----END PGP SIGNATURE-----
James Hatridge wrote:
Hi all..
I'm trying to get this to work. I've got a 1024k key working. But a few of my buddies are using 4096k keys. How can I work with this?
Use # gpg --gen-key from the command line to generate the key and specify 4096 bits as the option. 4096 bits is fairly paranoid. I use 1024 bits and make the key expire after a year. You might also like to export your key to a keyserver. This one took me a while. You can copy and paste to http://www.keyserver.net using a web browser, but first you have to export the key using something like #gpg --list-keys gpg: Warning: using insecure memory! /home/jdl/.gnupg/pubring.gpg ---------------------------- pub 1024D/17CA2F96 2003-03-23 John D Lamb <J.D.Lamb@btinternet.com> sub 1024g/F4420DE4 2003-03-23 [expires: 2004-03-22] This finds the key (17CA2F96). Then gpg --export -a 17CA2F96 To get the key in a form you can copy and paste. It was the -a that took a while for me ;-) -- JDL
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Check out the --send-keys command and the --keyserver option. Kind regards, Simon John Lamb wrote: | James Hatridge wrote: | |> Hi all.. |> |> I'm trying to get this to work. I've got a 1024k key working. But a |> few of my buddies are using 4096k keys. How can I work with this? | | | Use | | # gpg --gen-key | | from the command line to generate the key and specify 4096 bits as the | option. 4096 bits is fairly paranoid. I use 1024 bits and make the key | expire after a year. | | You might also like to export your key to a keyserver. This one took me | a while. You can copy and paste to http://www.keyserver.net using a web | browser, but first you have to export the key using something like | | #gpg --list-keys | gpg: Warning: using insecure memory! | /home/jdl/.gnupg/pubring.gpg | ---------------------------- | pub 1024D/17CA2F96 2003-03-23 John D Lamb <J.D.Lamb@btinternet.com> | sub 1024g/F4420DE4 2003-03-23 [expires: 2004-03-22] | | This finds the key (17CA2F96). Then | | gpg --export -a 17CA2F96 | | To get the key in a form you can copy and paste. It was the -a that took | a while for me ;-) | - -- Simon JF Heaton <simon.heaton@softwareag.co.uk> Principal Technical Consultant Software AG UK Ltd. Tel: +44(0) 1332 611000 Signature Fpr: 465D 6534 0768 B3EA C564 471B 0BD0 55CB D338 E1DA Encryption Fpr: 94E2 65D9 2473 D1BD 0374 BB22 30E8 7603 731F 6D82 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE+iwqvC9BVy9M44doRAqIzAKDGPO4NmmKhQXG+dpEZOjEcS1KamQCgh5hL I51hlxc5JP29/xtYu5uSgAg= =vF1C -----END PGP SIGNATURE-----
participants (3)
-
James Hatridge -
John Lamb -
Simon Heaton