Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WQwvS-0004tE-VJ for bitcoin-development@lists.sourceforge.net; Fri, 21 Mar 2014 10:43:47 +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 1WQwvR-00061s-Gn for bitcoin-development@lists.sourceforge.net; Fri, 21 Mar 2014 10:43:46 +0000 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1WQwvK-0001v8-OI for bitcoin-development@lists.sourceforge.net; Fri, 21 Mar 2014 11:43:38 +0100 Received: from e179064016.adsl.alicedsl.de ([85.179.64.16]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 21 Mar 2014 11:43:38 +0100 Received: from andreas by e179064016.adsl.alicedsl.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 21 Mar 2014 11:43:38 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: bitcoin-development@lists.sourceforge.net From: Andreas Schildbach Date: Fri, 21 Mar 2014 11:43:27 +0100 Message-ID: References: <20140320215208.GC88006@giles.gnomon.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: e179064016.adsl.alicedsl.de User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 In-Reply-To: <20140320215208.GC88006@giles.gnomon.org.uk> X-Enigmail-Version: 1.5.2 X-Spam-Score: -0.4 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -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] -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 SPF_HELO_PASS SPF: HELO matches SPF record 1.1 DKIM_ADSP_ALL No valid author signature, domain signs all mail -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -0.0 SPF_PASS SPF: sender matches SPF record X-Headers-End: 1WQwvR-00061s-Gn Subject: Re: [Bitcoin-development] Payment Protocol for Face-to-face Payments 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: Fri, 21 Mar 2014 10:43:47 -0000 +1 I couldn't do a better job at describing my motivation behind trying to stuff payment requests into QR codes. On 03/20/2014 10:52 PM, Roy Badami wrote: > On Thu, Mar 20, 2014 at 07:31:27PM +0100, Mike Hearn wrote: > >> Yes, this overlaps somewhat with the PKI signing in BIP70, but not >> entirely - you might want to serve unsigned payment requests, but >> still have confidentiality and authenticity for a local face to face >> transaction. The signing and encryption does different things > > I'm not sure if this what you're getting at, but in a common > face-to-face scenario, it really doesn't overlap so much (in that the > PKI in BIP70 isn't really helpful). > > It's not unusual, in a face-to-face transaction at a bricks-and-mortar > establishment, that you know neither the legal name of the entity > running the establishment, nor any electronic identifier (domain name, > email address) that might be presented to you in an X.509 certificate, > even if such a certificate is presented in the PaymentRequest. > > In many cases I want/need to simply be assured that I am paying "the > person/organisation which operates that machine behind the counter, > right there". > > In many ways I'll miss the simplicity of BIP21 QR codes for > face-to-face transactions - because in this use case the payment > protocol complicates (and in many cases weakens) the assurance that > you really are paying the entity that prepared the QR code. > > roy > > ------------------------------------------------------------------------------ > Learn Graph Databases - Download FREE O'Reilly Book > "Graph Databases" is the definitive new guide to graph databases and their > applications. Written by three acclaimed leaders in the field, > this first edition is now available. Download your free book today! > http://p.sf.net/sfu/13534_NeoTech >