Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.212.182 as permitted sender)
	client-ip=209.85.212.182; envelope-from=mh.in.england@gmail.com;
	helo=mail-wi0-f182.google.com; 
MIME-Version: 1.0
Sender: mh.in.england@gmail.com
In-Reply-To: <CAPkFh0tWykVJU-9mCTR95eqUF0B5TO-ZO7B3L0wf_QYAmAuuBA@mail.gmail.com>
References: <CAPkFh0tWykVJU-9mCTR95eqUF0B5TO-ZO7B3L0wf_QYAmAuuBA@mail.gmail.com>
Date: Mon, 25 May 2015 20:07:09 +0200
Message-ID: <CANEZrP2BChNrX-GKse82CtjeMe2Trt8CfaZDyvH2b85EGF+FeQ@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: =?UTF-8?Q?Emin_G=C3=BCn_Sirer?= <el33th4x0r@gmail.com>
Content-Type: multipart/alternative; boundary=f46d043bdabce645540516ebe0e1
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Virtual Notary.
Precedence: list

--f46d043bdabce645540516ebe0e1
Content-Type: text/plain; charset=UTF-8

Very nice Emin! This could be very useful as a building block for oracle
based services. If only there were opcodes for working with X.509 ;)

I'd suggest at least documenting in the FAQ how to extract the data from
the certificate:

openssl pkcs12 -in virtual-notary-cert-stocks-16070.p12 -nodes -passin
pass:"" | openssl x509 -text|less

That's good enough to get started, but I note two issues:


   1. X.509 is kind of annoying to work with: example code in popular
   languages/frameworks to extract the statement would be useful.

   2. The stock price plugin, at least, embeds the data as text inside the
   X.509 certificate. That's also not terribly developer friendly and risks
   parsing errors undermining security schemes built on it.

   The way I'd solve this is to embed either a protocol buffer or DER
   encoded structure inside the extension, so developers can extract the
   notarised data directly, without needing to do any additional parsing.

--f46d043bdabce645540516ebe0e1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Very nice Emin! This could be very useful as a building bl=
ock for oracle based services. If only there were opcodes for working with =
X.509 ;)<br><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div><br>=
</div><div>I&#39;d suggest at least documenting in the FAQ how to extract t=
he data from the certificate:</div><div><br></div><div>


<p class=3D""><span class=3D"">openssl pkcs12 -in virtual-notary-cert-stock=
s-16070.p12 -nodes -passin pass:&quot;&quot; | openssl x509 -text|less</spa=
n></p><p class=3D"">That&#39;s good enough to get started, but I note two i=
ssues:</p><p class=3D""></p><ol><li>X.509 is kind of annoying to work with:=
 example code in popular languages/frameworks to extract the statement woul=
d be useful.<br><br></li><li>The stock price plugin, at least, embeds the d=
ata as text inside the X.509 certificate. That&#39;s also not terribly deve=
loper friendly and risks parsing errors undermining security schemes built =
on it.<br><br>The way I&#39;d solve this is to embed either a protocol buff=
er or DER encoded structure inside the extension, so developers can extract=
 the notarised data directly, without needing to do any additional parsing.=
</li></ol><div><br></div><p></p></div></div></div></div>

--f46d043bdabce645540516ebe0e1--