From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Ro12P-0003WF-28 for garchives@archives.gentoo.org; Thu, 19 Jan 2012 23:04:57 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C177AE08BE; Thu, 19 Jan 2012 23:04:13 +0000 (UTC) Received: from mail-gy0-f181.google.com (mail-gy0-f181.google.com [209.85.160.181]) by pigeon.gentoo.org (Postfix) with ESMTP id 73BC2E09B5 for ; Thu, 19 Jan 2012 23:01:22 +0000 (UTC) Received: by ghbg19 with SMTP id g19so369670ghb.40 for ; Thu, 19 Jan 2012 15:01:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=oPxiRpREE3OmEHg1E0MYgCueXds7/V/EZE27s42jZTo=; b=gcgqaBXMnM2xwgd5bXxFbtb9zj7CRJSNbpduM+iRaKcsCpJU1EcFylLZvfarIOrYo4 vY/FKwoU3I96TDNMMCw+Uv67sceQfnMGJkuMnXqobDBCknGTP+Nk6AzS/kQiTZx6F4Tj aTTBp/a211hXeACJqghS3frmk36dhOJK1dx7g= Received: by 10.236.180.101 with SMTP id i65mr20208041yhm.120.1327014081935; Thu, 19 Jan 2012 15:01:21 -0800 (PST) Received: from [192.168.2.5] (adsl-98-95-147-47.jan.bellsouth.net. [98.95.147.47]) by mx.google.com with ESMTPS id i32sm2305774anm.22.2012.01.19.15.01.20 (version=SSLv3 cipher=OTHER); Thu, 19 Jan 2012 15:01:20 -0800 (PST) Message-ID: <4F18A0BF.6090805@gmail.com> Date: Thu, 19 Jan 2012 17:01:19 -0600 From: Dale User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0.1) Gecko/20120118 Firefox/9.0.1 SeaMonkey/2.6.1 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] S.O.P.A and P.I.P.A and the blackout. References: <4F175C04.309@comcast.net> <4F177008.7000209@gmail.com> <20120119014553.GA4137@eisen.fritz.box> <4F177B2A.3080004@gmail.com> <20120119082720.20eca1de@khamul.example.con> <4F17BDD3.7080803@gmail.com> <20120119165746.GB18074@eisen.lan> <4F1853B9.4030001@comcast.net> <4F18935B.3020302@gmail.com> In-Reply-To: X-Enigmail-Version: 1.3.4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: cb688aca-4b08-4a89-9276-32ba076635b5 X-Archives-Hash: 62f94553120ee2038b77b35b98074766 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"