From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YWXg2-0008LK-6u for bitcoin-development@lists.sourceforge.net; Fri, 13 Mar 2015 22:03:30 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.223.173 as permitted sender) client-ip=209.85.223.173; envelope-from=mh.in.england@gmail.com; helo=mail-ie0-f173.google.com; Received: from mail-ie0-f173.google.com ([209.85.223.173]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YWXg1-0000m2-95 for bitcoin-development@lists.sourceforge.net; Fri, 13 Mar 2015 22:03:30 +0000 Received: by iecsl2 with SMTP id sl2so128506843iec.1 for ; Fri, 13 Mar 2015 15:03:23 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.50.79.230 with SMTP id m6mr87351423igx.33.1426284203349; Fri, 13 Mar 2015 15:03:23 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.36.54.147 with HTTP; Fri, 13 Mar 2015 15:03:23 -0700 (PDT) In-Reply-To: References: Date: Fri, 13 Mar 2015 15:03:23 -0700 X-Google-Sender-Auth: -MvxgHV6oBuntwnwaD0Y_lJj5fk Message-ID: From: Mike Hearn To: Kalle Rosenbaum Content-Type: multipart/alternative; boundary=089e01229aaa4a2475051132abe2 X-Spam-Score: -0.5 (/) 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 (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1YWXg1-0000m2-95 Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Proof of Payment 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, 13 Mar 2015 22:03:30 -0000 --089e01229aaa4a2475051132abe2 Content-Type: text/plain; charset=UTF-8 > > As soon as that PaymentRequest leaves the wallet on its way to the hotel > server, it is up for grabs > Is it? I'm assuming TLS is being used here. And the hotel server also has a copy of the PaymentRequest, as the hotel actually issued it and that's how they're deciding the receipt is valid. So I don't know how it could be stolen unless the attacker can break TLS. --089e01229aaa4a2475051132abe2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
As soon as that PaymentReq= uest leaves the wallet on its way to the hotel server, it is up for grabs <= /div>

Is it? I'm assuming TLS is = being used here. And the hotel server also has a copy of the PaymentRequest= , as the hotel actually issued it and that's how they're deciding t= he receipt is valid. So I don't know how it could be stolen unless the = attacker can break TLS.
--089e01229aaa4a2475051132abe2--