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 1Ro3LK-0001XK-Jo for garchives@archives.gentoo.org; Fri, 20 Jan 2012 01:32:38 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0C856E0A82; Fri, 20 Jan 2012 01:32:29 +0000 (UTC) Received: from mail-yx0-f181.google.com (mail-yx0-f181.google.com [209.85.213.181]) by pigeon.gentoo.org (Postfix) with ESMTP id C1310E0936 for ; Fri, 20 Jan 2012 01:31:26 +0000 (UTC) Received: by yenr8 with SMTP id r8so37443yen.40 for ; Thu, 19 Jan 2012 17:31:26 -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=8E5omCdzo5pvDarC+zZlTHFtMRzjXI6jajuGEywaGNQ=; b=xSdu9ebFt2x9YYtY9ENT4Qv/eF0z7gMwNDl0yfk038Iq57jWKYY8qLOwX+iaTVsX45 eC12VEljJ3XXtssmCq1mY3BBZCd0EgrVCRvQ9G0478+ipwSLzLXdIvrtjrpuQEc96Lt7 7oFpkSp9an0hn7qeX8/uO5heGuwebp4Fy+U/U= Received: by 10.236.175.164 with SMTP id z24mr11209038yhl.84.1327023086119; Thu, 19 Jan 2012 17:31:26 -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 y14sm3440036anm.10.2012.01.19.17.31.24 (version=SSLv3 cipher=OTHER); Thu, 19 Jan 2012 17:31:25 -0800 (PST) Message-ID: <4F18C3EB.4080206@gmail.com> Date: Thu, 19 Jan 2012 19:31:23 -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> <4F189CBC.2050308@comcast.net> <4F18A54C.2010400@gmail.com> <201201200005.38172.michaelkintzios@gmail.com> In-Reply-To: <201201200005.38172.michaelkintzios@gmail.com> X-Enigmail-Version: 1.3.4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: 22c91a7e-11eb-454a-abc4-986b375980c0 X-Archives-Hash: 52934d50e4e48187a7defe27e1d9131b Mick wrote: > On Thursday 19 Jan 2012 23:20:44 Dale wrote: >> Chris Walters wrote: > >> 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. :/ > > Better than that. > > Readers (all that have access to this list) can a)see that you have signed it > and b)rest assured that no one has tampered with its content since you signed. > If anyone intercepted the message mid-air and changed its content, your > signature would show as bad in the recipients mail client (assuming they have > a GnuPG/PGP compatible client). > > BTW, your signature is not showing in Kmail ... are you using inline or > opengpg/smime format? > > I don't have mine set up to sign them all. I did a couple to see if it worked or not. Whenever I sign a message, it asks for the password. It is quite a long password and I don't want to type it in every time I send something. >>> 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 > >> 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. > > To avoid an easy misunderstanding about what the "password" does: > > You are asked for a passphrase not because Chris used that passphrase to > encrypt the message he sent you with (that would have been symmetric > encryption and both of you would need to know in advance the secret > passphrase). Instead, you are asked for a passphrase to decrypt your own > private gpg key which is stored in encrypted format on your hard drive for > security purposes. The private key once decrypted and loaded in memory will > be used by your openpgp application to decrypt the message sent by Chris. > > This is asymmetric encryption: a sender can use your public key and their > private key to encrypt a message to you, which only you can decrypt with your > private key and the sender's public key. Look at the picture on the right in > this page: > > http://en.wikipedia.org/wiki/Public-key_cryptography > > HTH The password I was talking about is the one when I send a message. It does ask for the password when Paul was sending a message. Those were off list tho. Anyway, when I put the password in, I can read the email. Otherwise, I can't read anything. How sure are we that there is no back door the Government has to bypass this? Are we 99% sure or about 50/50 with our fingers crossed? 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"