From e388eba06a7b29a0343f2be0efe37d74d0a663c8 Mon Sep 17 00:00:00 2001 From: Mike Hearn <mike@plan99.net> Date: Fri, 13 Mar 2015 15:03:23 -0700 Subject: Re: [Bitcoin-development] Proof of Payment --- d0/b96f714ea1b1b81aaecf47a286f11d8a33137f | 91 +++++++++++++++++++++++++++++++ 1 file changed, 91 insertions(+) create mode 100644 d0/b96f714ea1b1b81aaecf47a286f11d8a33137f diff --git a/d0/b96f714ea1b1b81aaecf47a286f11d8a33137f b/d0/b96f714ea1b1b81aaecf47a286f11d8a33137f new file mode 100644 index 000000000..7afbe1045 --- /dev/null +++ b/d0/b96f714ea1b1b81aaecf47a286f11d8a33137f @@ -0,0 +1,91 @@ +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 <mh.in.england@gmail.com>) 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 <bitcoin-development@lists.sourceforge.net>; + 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: <CAPswA9yicPa=4peZdjGXhrY64WwABj9rkq3vF5Lv1cEqhEER5w@mail.gmail.com> +References: <CAPswA9zzVDxW8_WXg5833r2Z4pxZOppYtNLHMQ=Nw-H72cMz7w@mail.gmail.com> + <CANEZrP0V4wg4X1ASx9_+ONP749s9TD3PcemA_wyjYvgZDxh+WA@mail.gmail.com> + <CAPswA9yicPa=4peZdjGXhrY64WwABj9rkq3vF5Lv1cEqhEER5w@mail.gmail.com> +Date: Fri, 13 Mar 2015 15:03:23 -0700 +X-Google-Sender-Auth: -MvxgHV6oBuntwnwaD0Y_lJj5fk +Message-ID: <CANEZrP0U6MF7ibvb8gTdPbeczBn5UiOFN_NnMnOAuwr4sNFUXw@mail.gmail.com> +From: Mike Hearn <mike@plan99.net> +To: Kalle Rosenbaum <kalle@rosenbaum.se> +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 <bitcoin-development@lists.sourceforge.net> +Subject: Re: [Bitcoin-development] Proof of Payment +X-BeenThere: bitcoin-development@lists.sourceforge.net +X-Mailman-Version: 2.1.9 +Precedence: list +List-Id: <bitcoin-development.lists.sourceforge.net> +List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> +List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> +List-Post: <mailto:bitcoin-development@lists.sourceforge.net> +List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> +List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=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 + +<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo= +ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c= +cc solid;padding-left:1ex"><div dir=3D"ltr"><div>As soon as that PaymentReq= +uest leaves the wallet on its way to the hotel server, it is up for grabs <= +/div></div></blockquote><div><br></div><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.</div></div></div></div> + +--089e01229aaa4a2475051132abe2-- + + -- cgit v1.2.3