-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 A couple weeks back, someone suggested I publish my public key to a server. I just learned that by not publishing it, it is causing people problems when they try to read my email. I can simply attach the key to the same mail that I signed, and the trust thereby established is as good as the trust you have in the authenticity of my membership on this list. Where can I learn more about this? In a hurry. STH -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFANx1bH2SF0i7rrGwRAlXnAJ9Rf7BPZOWlS/CYuQ8Uli8FrElacACfVoQC DDZSwWm6UNYOLOiI6uMp6os= =5PwA -----END PGP SIGNATURE-----
On Saturday 21 February 2004 08:56, Steven T. Hatton wrote:
A couple weeks back, someone suggested I publish my public key to a server. I just learned that by not publishing it, it is causing people problems when they try to read my email. I can simply attach the key to the same mail that I signed, and the trust thereby established is as good as the trust you have in the authenticity of my membership on this list.
Where can I learn more about this? In a hurry.
STH
Steven
In order to publish your key to a public key server, you first have to
generate a public key block for your key. This has to include ONLY your key,
not others already on your keyring. Proceed as follows.
1. List your keys (most of output omitted).
dbarnes@beverly:~> gpg --list-keys
/home/dbarnes/.gnupg/pubring.gpg
--------------------------------
pub 1024D/384446AF 2004-02-12 David Barnes
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday 21 February 2004 08:21 am, David Barnes wrote:
On Saturday 21 February 2004 08:56, Steven T. Hatton wrote:
A couple weeks back, someone suggested I publish my public key to a server. I just learned that by not publishing it, it is causing people problems when they try to read my email. I can simply attach the key to the same mail that I signed, and the trust thereby established is as good as the trust you have in the authenticity of my membership on this list.
Where can I learn more about this? In a hurry.
STH
Steven
In order to publish your key to a public key server, you first have to generate a public key block for your key. This has to include ONLY your key, not others already on your keyring. Proceed as follows.
Thanks! It worked great. As I was looking at the Key Management console for KGpg, I discovered a means to publish from there. I haven't checked to see if it worked. BTW. Will the keys magically propagate around the world, or do I have to point people to the server now? I guess I really need to take a break and read up on this. I've done a lot of work with SSL and X509 PKI, but not with pgp.
David Barnes
STH -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFAN2e8H2SF0i7rrGwRAvnHAJ9WQtEKlRDcmy4+HItuT7Ar0HfMNQCaA8q4 +uuqI8URrIadyWQIi7mFCWI= =96i8 -----END PGP SIGNATURE-----
The Saturday 2004-02-21 at 13:21 -0000, David Barnes wrote:
In order to publish your key to a public key server, you first have to
I wonder where can a list of servers be found :-? By the way, when reading your email, I got an unexpected error message: |gpg: WARNING: using insecure memory! |gpg: please see http://www.gnupg.org/faq.html for more information |gpg: CRC error; c3f145 - 6a60cc | |gpg: Ohhhh jeeee: mpi crosses packet border |secmem usage: 0/0 bytes in 0/0 blocks of pool 0/16384 | |Please press Enter / Return a couple times to continue. |If you want to cancel, press Control-C. I'm worried about the CRC error, and the "Ohhhh jeeee" thing - but this might have been caused by your email containing pastes of a key in the middle of a message, and this confusing Pine. -- Cheers, Carlos Robinson
On Saturday 21 February 2004 14:53, Carlos E. R. wrote:
The Saturday 2004-02-21 at 13:21 -0000, David Barnes wrote:
In order to publish your key to a public key server, you first have to
I wonder where can a list of servers be found :-?
By the way, when reading your email, I got an unexpected error message: |gpg: WARNING: using insecure memory! |gpg: please see http://www.gnupg.org/faq.html for more information |gpg: CRC error; c3f145 - 6a60cc | |gpg: Ohhhh jeeee: mpi crosses packet border |secmem usage: 0/0 bytes in 0/0 blocks of pool 0/16384 | |Please press Enter / Return a couple times to continue. |If you want to cancel, press Control-C.
I'm worried about the CRC error, and the "Ohhhh jeeee" thing - but this might have been caused by your email containing pastes of a key in the middle of a message, and this confusing Pine.
-- Cheers, Carlos Robinson
The insecure memory warning is usually because the gpg binary is not installed setuid root by default - see the file /usr/share/doc/packages/gpg/ README.SuSE. The other warnings - don't know, but I suspect you're right. -- Best Regards David Barnes
The Saturday 2004-02-21 at 15:22 -0000, David Barnes wrote:
The insecure memory warning is usually because the gpg binary is not installed setuid root by default - see the file /usr/share/doc/packages/gpg/ README.SuSE.
I know, I don't care :-) -- because this is a personal machine, no users, and if there were, I'm the root.
The other warnings - don't know, but I suspect you're right.
Ok. -- Cheers, Carlos Robinson
participants (3)
-
Carlos E. R. -
David Barnes -
Steven T. Hatton