Paul Hartman wrote:
> There are basically 2 things PGP/GPG normally does for emails: signing > and encrypting. They are not mutually exclusive. > > Signing (like you see on a lot of messages on this list, for example) > is about the person who SENT the message. It lets you verify that the > person who wrote the message is who you think they are, and that the > contents of the message itself have not been altered. > > Encrypting is about the person RECEIVING the message. If you encrypt, > it makes it so the message cannot be read by anyone except for the > recipients you specified when encrypting it. (The sender is usually > added to the encrypted recipients automatically, in case he needs to > read his own sent message at a later date). Encryption is obviously in > very bad taste on a public mailing list. :) > > So if you send a message that is both signed + encrypted, it will > verify the identity of the sender as well as restrict the ability to > read to only the people the sender wants. > > You can also use PGP keys for authentication (with an OpenPGP > smartcard), and for signing files, which works just like signing > email. > > I think I get this now. When I sign the message, someone else opens it, then it shows up that I signed it with the digital signature. Anyone can read it tho. It's public as any normal email. Everyone just knows it came from my rig is all. When I encypt a message, only the person that I select the keys for can open it. Example. I hit send and select your name in the little box that pops up. Then only you can see the message but others on the list can't since I only sent you the keys. Am I close? I'm using Seamonkey by the way. When I hit send, I get a pop up window that lists all the key thingys. I'm not sure how other clients do this. I select which keys in that thing then it sends it. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words! Miss the compile output? Hint: EMERGE_DEFAULT_OPTS="--quiet-build=n"
