Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] 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 1YPry2-0007Y2-Sb for bitcoin-development@lists.sourceforge.net; Mon, 23 Feb 2015 12:18:30 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.212.175 as permitted sender) client-ip=209.85.212.175; envelope-from=mh.in.england@gmail.com; helo=mail-wi0-f175.google.com; Received: from mail-wi0-f175.google.com ([209.85.212.175]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YPry1-0000qT-SJ for bitcoin-development@lists.sourceforge.net; Mon, 23 Feb 2015 12:18:30 +0000 Received: by mail-wi0-f175.google.com with SMTP id r20so16368378wiv.2 for <bitcoin-development@lists.sourceforge.net>; Mon, 23 Feb 2015 04:18:23 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.194.61.51 with SMTP id m19mr21772322wjr.39.1424693903819; Mon, 23 Feb 2015 04:18:23 -0800 (PST) Sender: mh.in.england@gmail.com Received: by 10.194.188.11 with HTTP; Mon, 23 Feb 2015 04:18:23 -0800 (PST) In-Reply-To: <mcf4kk$pl0$1@ger.gmane.org> References: <20150222190839.GA18527@odo.localdomain> <54EA5A1C.2020701@AndySchroder.com> <54EA60D9.8000001@voskuil.org> <54EA66F5.2000302@AndySchroder.com> <mcdu6b$j11$1@ger.gmane.org> <54EAD884.8000205@AndySchroder.com> <mcet2t$qav$1@ger.gmane.org> <54EAFC1C.9080502@voskuil.org> <CANEZrP0XYfnarvN5H_NeOGyO8RLBSGyGxv7M63MSrAd_HXj1OQ@mail.gmail.com> <mcf4kk$pl0$1@ger.gmane.org> Date: Mon, 23 Feb 2015 13:18:23 +0100 X-Google-Sender-Auth: -i7Q5R_hjZm2H1PaPy56Aluu-ds Message-ID: <CANEZrP3g_HT9cZepcD6rAgWV10H6aJRR7nVTtYwhBcAbx_0nfQ@mail.gmail.com> From: Mike Hearn <mike@plan99.net> To: Andreas Schildbach <andreas@schildbach.de> Content-Type: multipart/alternative; boundary=047d7b66fa5f0d0a34050fc06634 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: 1YPry1-0000qT-SJ Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net> Subject: Re: [Bitcoin-development] Bitcoin at POS using BIP70, NFC and offline payments - implementer feedback 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: Mon, 23 Feb 2015 12:18:31 -0000 --047d7b66fa5f0d0a34050fc06634 Content-Type: text/plain; charset=UTF-8 > > I read from your answer that even if we use ECDHE, we can't use it for > every situation. > Which situations do you mean? I think it can be used in every situation. It's the opposite way around - a fixed session key in the URI cannot be used in every situation. --047d7b66fa5f0d0a34050fc06634 Content-Type: text/html; charset=UTF-8 <div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I read from your answer that even if we use ECDHE, we can't use it for<br> every situation.<br></blockquote><div><br></div><div>Which situations do you mean? I think it can be used in every situation. It's the opposite way around - a fixed session key in the URI cannot be used in every situation.</div></div></div></div> --047d7b66fa5f0d0a34050fc06634--