From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) id 1W2jtv-0008Cf-QV for bitcoin-development@lists.sourceforge.net; Mon, 13 Jan 2014 15:58:07 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.219.41 as permitted sender) client-ip=209.85.219.41; envelope-from=mh.in.england@gmail.com; helo=mail-oa0-f41.google.com; Received: from mail-oa0-f41.google.com ([209.85.219.41]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1W2jtu-0005w4-Pi for bitcoin-development@lists.sourceforge.net; Mon, 13 Jan 2014 15:58:07 +0000 Received: by mail-oa0-f41.google.com with SMTP id i4so7231162oah.0 for ; Mon, 13 Jan 2014 07:58:01 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.182.143.103 with SMTP id sd7mr1421463obb.70.1389628681380; Mon, 13 Jan 2014 07:58:01 -0800 (PST) Sender: mh.in.england@gmail.com Received: by 10.76.99.112 with HTTP; Mon, 13 Jan 2014 07:58:01 -0800 (PST) In-Reply-To: <20140113133746.GI38964@giles.gnomon.org.uk> References: <20140106120338.GA14918@savin> <20140110102037.GB25749@savin> <20140113133746.GI38964@giles.gnomon.org.uk> Date: Mon, 13 Jan 2014 16:58:01 +0100 X-Google-Sender-Auth: k7Rd2Bxo1HyCPdndIm6BPGVhe_U Message-ID: From: Mike Hearn To: Roy Badami Content-Type: multipart/alternative; boundary=e89a8ff1ce9eec69d704efdc2323 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: 1W2jtu-0005w4-Pi Cc: "bitcoin-development@lists.sourceforge.net" Subject: Re: [Bitcoin-development] Stealth Addresses 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: Mon, 13 Jan 2014 15:58:08 -0000 --e89a8ff1ce9eec69d704efdc2323 Content-Type: text/plain; charset=UTF-8 On Mon, Jan 13, 2014 at 2:37 PM, Roy Badami wrote: > That does require trusting the third party not to later tamper with > the payment request, though. You have to trust the billboard owner too. If you're relying on a third party to relay a payment instruction, that will always be an issue, hence the signing. Signing a payment request for an individual is easy, anyway, depending on the kind of ID you want. If you want to sign with an email address, just go here with a browser like Chrome/Safari/IE that uses the system keystore: http://www.comodo.com/home/email-security/free-email-certificate.php They'll send you an email, you click the link to verify, and a cert will be generated and installed by your web browser. It's actually easier than signing up for a website. There are lots of other places that do it for free too, I just picked the first one from a google search for [free email certificate]. Once you've got that in your keystore, a wallet app can quite easily be told to sign payment requests with your email address. For a billboard I guess you'd probably be an organisation or company instead, though an email address can work there too as long as you have a well known domain name. --e89a8ff1ce9eec69d704efdc2323 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On M= on, Jan 13, 2014 at 2:37 PM, Roy Badami <roy@gnomon.org.uk> = wrote:
That= does require trusting the third party not to later tamper with
the payment request, though.

You have to tr= ust the billboard owner too. If you're relying on a third party to rela= y a payment instruction, that will always be an issue, hence the signing.

Signing a payment request for an individual is easy, an= yway, depending on the kind of ID you want. If you want to sign with an ema= il address, just go here with a browser like Chrome/Safari/IE that uses the= system keystore:


They'= ll send you an email, you click the link to verify, and a cert will be gene= rated and installed by your web browser. It's actually easier than sign= ing up for a website. There are lots of other places that do it for free to= o, I just picked the first one from a google search for [free email certifi= cate].

Once you've got that in your keystore, a wallet app= can quite easily be told to sign payment requests with your email address.=

For a billboard I guess you'd probably be an = organisation or company instead, though an email address can work there too= as long as you have a well known domain name.
--e89a8ff1ce9eec69d704efdc2323--