From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Tmw3u-0003Xg-GD for bitcoin-development@lists.sourceforge.net; Mon, 24 Dec 2012 00:38:34 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of m.gmane.org designates 80.91.229.3 as permitted sender) client-ip=80.91.229.3; envelope-from=gcbd-bitcoin-development@m.gmane.org; helo=plane.gmane.org; Received: from plane.gmane.org ([80.91.229.3]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1Tmw3s-0003Vq-C3 for bitcoin-development@lists.sourceforge.net; Mon, 24 Dec 2012 00:38:34 +0000 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Tmw3w-0002kr-9p for bitcoin-development@lists.sourceforge.net; Mon, 24 Dec 2012 01:38:36 +0100 Received: from 184.169.9.215 ([184.169.9.215]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 24 Dec 2012 01:38:36 +0100 Received: from tyrell.elden by 184.169.9.215 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 24 Dec 2012 01:38:36 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: bitcoin-development@lists.sourceforge.net From: Elden Tyrell Date: Sun, 23 Dec 2012 16:38:09 -0800 Message-ID: References: <20121129185330.GE6368@giles.gnomon.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 184.169.9.215 User-Agent: Unison/2.1.8 X-Spam-Score: 0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (tyrell.elden[at]gmail.com) -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [80.91.229.3 listed in list.dnswl.org] -0.0 SPF_HELO_PASS SPF: HELO matches SPF record 0.0 DKIM_ADSP_CUSTOM_MED No valid author signature, adsp_override is CUSTOM_MED -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -0.0 SPF_PASS SPF: sender matches SPF record 0.9 RCVD_NUMERIC_HELO Received: contains an IP address used for HELO 1.2 NML_ADSP_CUSTOM_MED ADSP custom_med hit, and not from a mailing list X-Headers-End: 1Tmw3s-0003Vq-C3 Subject: Re: [Bitcoin-development] Payment Protocol Proposal: Invoices/Payments/Receipts X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Dec 2012 00:38:34 -0000 On 2012-12-21 17:05:21 +0000, Stephen Pair said: > Also, identity is one thing, an elaborate trust based identity > verification system (like CA's) is a whole other thing. Your distinction between "identity" and "trust-based identity" is one of the most important insights to emerge from this thread. Thank you for pointing this out. > the first task at hand is to implement secure, private messaging... > it's easy to do and you don't need to solve the PKI problem.