[Enigmail] Hello Enigmail, new user here!

[John Clizbe]

Dogssup wrote:
> Open source is awesome :)
> 
> Now, I don't know exactly what I'm doing but I'm including my public key
> at the bottom.

That's OK. Most folks just send their key to one of the keysevers and recipients
client software is usually configured to fetch the needed key from the keyserver
network.

> On peoples web pages they include their public key. Do I copy and paste
> (import) this into Enigmail to start encryption correspondence? 

No, Enigmail just calls GnuPG to do the crypto-work.

> How do I know this public key has not been altered and/or the person I intend
> my encrypted mail to go? For this reason, I'd think putting the public key
> on a server is safer to avoid the risk of it being altered?

Could you define what you mean by altered? The packets within the key have
integrity mechanisms built-in that will keep a key from importing if it's
altered/mangled in transit.

> Sorry for all the questions!

That's what we're here for


-- 
John P. Clizbe                      Inet:   John (a) Mozilla-Enigmail.org
You can't spell fiasco without SCO. hkp://keyserver.gingerbear.net  or
Send email with subject HELP to  pgp-public-keys at keyserver.gingerbear.net

"what's the key to success?"        / "two words: good decisions."
"what's the key to good decisions?" /  "one word: experience."
"how do i get experience?"          / "two words: bad decisions."

"Just how do the residents of Haiku, Hawai'i hold conversations?"

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 679 bytes
Desc: OpenPGP digital signature
Url : http://www.mozdev.org/pipermail/enigmail/attachments/20080310/f852bec6/attachment.bin