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 1Ro1Is-0006Vz-Tk for garchives@archives.gentoo.org; Thu, 19 Jan 2012 23:21:59 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 41072E09B5; Thu, 19 Jan 2012 23:21:50 +0000 (UTC) Received: from mail-yw0-f53.google.com (mail-yw0-f53.google.com [209.85.213.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 3881BE09AF for ; Thu, 19 Jan 2012 23:20:47 +0000 (UTC) Received: by yhjj56 with SMTP id j56so363366yhj.40 for ; Thu, 19 Jan 2012 15:20:46 -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=KSIDWRsKk0Cw0IgWJiZ2eQzmXE+yCN/FiVbdGaVweHw=; b=Qnp+NkDee1TK0wGdgjppplhwQ2QRm9a653Vkx8nKqRaVti4pE99IBFjn7QN64GNzVv fzt39RB6qkWiiEOyJ3NB6wk2Y9JhiB5vc3QK5YhuV37K31WHoQb/qsDNiMuRh2wvTWYR 9/uu4Kw/UmPcs0xEnPZCgZvoKpdgfXkErUv78= Received: by 10.236.145.102 with SMTP id o66mr41307679yhj.28.1327015246748; Thu, 19 Jan 2012 15:20:46 -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 o16sm2486788ank.14.2012.01.19.15.20.45 (version=SSLv3 cipher=OTHER); Thu, 19 Jan 2012 15:20:46 -0800 (PST) Message-ID: <4F18A54C.2010400@gmail.com> Date: Thu, 19 Jan 2012 17:20:44 -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> <4F189CBC.2050308@comcast.net> In-Reply-To: <4F189CBC.2050308@comcast.net> X-Enigmail-Version: 1.3.4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: e0ea0b06-b14f-4802-bc91-8fe2a471f62b X-Archives-Hash: d9be404ab009722708cfb59f78da8952 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chris Walters wrote: > On 1/19/2012 05:04 PM, Dale wrote: >> Chris Walters wrote: >>> >>> This is a test. Enigmail has been trying to use a revoked and >>> expired key to sign my messages, lately. >>> >>> Chris >>> >> >> >> I have a question now. I got a message from Paul Hartman and >> replied to it, off list, and it was encrypted and I hope my reply >> was too. My question is this. How do you make a email that only >> the sender and receiver can read? As a example. I'm talking to >> a Doctor or a lawyer and I don't want anyone but that person to >> see the email. How do I do that? Can that be done. > > Yes, see below. It looks like you are using a web interface > (Firefox) to send and reply to messages. I would suggest emerging > Thunderbird (emerge -av thunderbird). There is an add on called > Enigmail for this mail client that makes encrypting, signing and > decrypting messages, much easier. You need gnupg, as well. > Close. Sort of. I actually use Seamonkey as my emailly program. >> The message that I am repying to appears to be something, >> encypted maybe, but I think anyone on this list that uses the >> tool can read it. Am I correct? > > If the message is encrypted to them, then yes. If not, no. You > need a secret key to decrypt a message that is encrypted, and if > anyone seeing it is not on the list of recipients, they will not > have that key. > I'm starting to see this now. When I sign a message, it is public but people are assured that it came from me. Sort of like having a check with a picture ID that matches. :/ >> I'm trying to get a full understanding of this thing. Ya'll know >> how I am. lol > > With OpenPGP or PGP/MIME, you would have to share your public key > with the other party - this would allow that party to encrypt > messages to you. You would also have to have the public key of the > other party to encrypt to them. > > For example, if you wanted to encrypt to me, you'd have to retrieve > my public key from a keyserver or I'd have to send it to you. You > would have to either sign a message (and have uploaded your public > key to a keyserver), or send me your public key. > > You could then encrypt a message to me, and you could add yourself > to the recipient list so you could read it. Then, when I received > the message, I would be prompted for my secret key's passphrase - > this would allow decryption of the message. Providing that I > replied to you and chose the "encrypt" option, the entire message, > including any quotes would be encrypted. > > Hope this helps, Chris > > -- Multibooting: wearing two socks of different colors and types, > with two different boots... ;) > So, this is why when I want to sign a message it asks me for the password. I thought it was trying to do something wrong. Made me scratch my head. Mud is clearing up a bit. 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" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8YpUwACgkQiBoxVpK2GMCz4QCeNBRDf8wmErruB5SVREcra4uu 6dQAnRnR8OuS0Mo5jcBnLNRGug0hkhK/ =XWWa -----END PGP SIGNATURE-----