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 1Ro18J-0004m0-GQ for garchives@archives.gentoo.org; Thu, 19 Jan 2012 23:11:03 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D20B4E0986; Thu, 19 Jan 2012 23:10:34 +0000 (UTC) Received: from mail-gx0-f181.google.com (mail-gx0-f181.google.com [209.85.161.181]) by pigeon.gentoo.org (Postfix) with ESMTP id 0368EE0A86 for ; Thu, 19 Jan 2012 23:07:06 +0000 (UTC) Received: by ggnv2 with SMTP id v2so394792ggn.40 for ; Thu, 19 Jan 2012 15:07:06 -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=HPXq4QJRRm8fNoKfD5rQaMGJ0u5/oDPD2UPOMqp/Uh4=; b=YwwhfVuy9I0C/7+hdfi56NdDK64pULnDel5TSf90zak7B3nePWevsz/hCPE5XXN1pd VFI+OIfoCFRLsqOTuJvDro7j4TIR17ww8JbX3GIKM1hGhRXI8KEDobdsn/ZAHcdEoYhL gFXqVJTcmNO04hI42rVUSQHFCeG8lrcS9XLPk= Received: by 10.236.46.232 with SMTP id r68mr42366572yhb.80.1327014426508; Thu, 19 Jan 2012 15:07:06 -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 p63sm1579019yhj.22.2012.01.19.15.07.04 (version=SSLv3 cipher=OTHER); Thu, 19 Jan 2012 15:07:05 -0800 (PST) Message-ID: <4F18A217.7090603@gmail.com> Date: Thu, 19 Jan 2012 17:07:03 -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> <20120120004216.43a826eb@khamul.example.con> In-Reply-To: <20120120004216.43a826eb@khamul.example.con> X-Enigmail-Version: 1.3.4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: 323f08f3-88fa-4f31-b764-cef03edffadc X-Archives-Hash: f45e7659715c696024509bbe77211f92 Alan McKinnon wrote: > On Thu, 19 Jan 2012 16:04:11 -0600 Dale > wrote: > >> Chris Walters wrote: >>> On 1/19/2012 11:57 AM, Frank Steinmetzger wrote: >>>> On Thu, Jan 19, 2012 at 12:53:07AM -0600, Dale wrote: >>>> >>>>> While on this subject, sort of. Who on here as their email >>>>> set up to encrypt and decrypt emails? I want to test some >>>>> things OFF LIST. >>>> >>>> Well, if you had signed your mail, then I could write you >>>> encrypted. :) >>> >>> 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. >> >> 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? >> >> I'm trying to get a full understanding of this thing. Ya'll know >> how I am. lol > > Well we first need to be accurate. It's not a case that only you > and Paul can read the encrypted mail. It's a case that only a > machine holding the necessary private key can decrypt it, and then > the mail can be read in plain text. Not quite the same thing as > what you said, as private keys can be stolen. > > If Paul encrypted the mail using your public key, then only the > private key you hold can decrypt it. Similarly, if you encrypt a > mail to Paul using his public key, then only Paul's private key can > decrypt it. > > There's no known way to decrypt a mail like that without the > single private key needed (this works exactly like https traffic to > your bank). I feel very confident saying "no known way" as cracking > that puzzle has been the Holy Grail of maths prizes for 40 years > and no-one has announced success. Seeing as mathematicians are a > vain lot, and the one that accomplishes this feat with be showered > with honour and glory for all time (making Einstein look like a > child), it's a safe assumption that it hasn't been done yet. > > To check if the mail was encrypted, simply tell EnigMail to not > decrypt it. It will show as gobbledegook, then only the recipient > can decrypt it (as long as the private key stays safe). > > To make this all work, you need to share public keys with each > other. But you don't need to do it in secret as the public keys > are, well, public. So you stick them on a key server where the > other guy can retrieve them and away you go, profit!!! There's a > few other steps you should do to establish trust in the public key > (they can be forged) but that's beyond the scope of explaining how > the keys work. > > The answer to your question is then yes. > > I suppose next you'll be wanting to know what fields to fill in in > your specific mail app to enable it your end, right? > > > > I don't think so. I been chatting with Paul off list. I can open his encypted emails and he can open mine. I think we call that success? I think I got this now. I got one more message to read tho. Getting it explained in more than one way helps me. I have to have that light bulb moment. ;-) 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"