Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <gavinandresen@gmail.com>) id 1VZuyU-0004NO-Sr
	for bitcoin-development@lists.sourceforge.net;
	Sat, 26 Oct 2013 03:55:42 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 74.125.82.175 as permitted sender)
	client-ip=74.125.82.175; envelope-from=gavinandresen@gmail.com;
	helo=mail-we0-f175.google.com; 
Received: from mail-we0-f175.google.com ([74.125.82.175])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1VZuyU-00032Q-4Y
	for bitcoin-development@lists.sourceforge.net;
	Sat, 26 Oct 2013 03:55:42 +0000
Received: by mail-we0-f175.google.com with SMTP id t61so4676780wes.34
	for <bitcoin-development@lists.sourceforge.net>;
	Fri, 25 Oct 2013 20:55:36 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.180.208.2 with SMTP id ma2mr1051103wic.52.1382759735928;
	Fri, 25 Oct 2013 20:55:35 -0700 (PDT)
Received: by 10.194.156.163 with HTTP; Fri, 25 Oct 2013 20:55:35 -0700 (PDT)
In-Reply-To: <CAAS2fgRRobkE2GdYomtJof7HCH-9ZczE9EBj7DBS-pCGscUSNQ@mail.gmail.com>
References: <CAAS2fgRRobkE2GdYomtJof7HCH-9ZczE9EBj7DBS-pCGscUSNQ@mail.gmail.com>
Date: Sat, 26 Oct 2013 13:55:35 +1000
Message-ID: <CABsx9T3NCpD19NehONkAdJXH=pS=GwDM044hFY_Hws-vkJcgBA@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Gregory Maxwell <gmaxwell@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c38dfcdeaf1204e99cd6dc
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
	(gavinandresen[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	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: 1VZuyU-00032Q-4Y
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Payment protocol for onion URLs.
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: Sat, 26 Oct 2013 03:55:43 -0000

--001a11c38dfcdeaf1204e99cd6dc
Content-Type: text/plain; charset=ISO-8859-1

On Sat, Oct 26, 2013 at 1:31 PM, Gregory Maxwell <gmaxwell@gmail.com> wrote:

> ....

This would give us an fully supported option which is completely CA
> free... it would only work for tor sites, but the people concerned
> about CA trechery are likely to want to use tor in any case.
>
> Thoughts?
>

I think a tiny number of people would use it, so from a purely engineering
priority perspective my initial reaction is "not worth it."

However, as a demonstration of the flexibility of the payment protocol and
because it is a really nifty idea that will give lots of people warm
fuzzies I think you should do it and we should pull it.

-- 
--
Gavin Andresen

--001a11c38dfcdeaf1204e99cd6dc
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Sat, Oct 26, 2013 at 1:31 PM, Gregory Maxwell <span dir=
=3D"ltr">&lt;<a href=3D"mailto:gmaxwell@gmail.com" target=3D"_blank">gmaxwe=
ll@gmail.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=
=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">....=A0</blockquote><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex">

This would give us an fully supported option which is completely CA<br>
free... it would only work for tor sites, but the people concerned<br>
about CA trechery are likely to want to use tor in any case.<br>
<br>
Thoughts?<br>
</blockquote></div><div class=3D"gmail_extra"><br></div>I think a tiny numb=
er of people would use it, so from a purely engineering priority perspectiv=
e my initial reaction is &quot;not worth it.&quot;</div><div class=3D"gmail=
_extra">
<br></div><div class=3D"gmail_extra">However, as a demonstration of the fle=
xibility of the payment protocol and because it is a really nifty idea that=
 will give lots of people warm fuzzies I think you should do it and we shou=
ld pull it.<br clear=3D"all">
<div><br></div>-- <br>--<br>Gavin Andresen<br>
</div></div>

--001a11c38dfcdeaf1204e99cd6dc--