📅 Original date posted:2015-05-25
📝 Original message: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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150525/eae53ab1/attachment.html>;
Mike Hearn [ARCHIVE] /
npub17t…4qgyd
2023-06-07 15:35:31
in reply to nevent1q…05xf
Author Public Key
npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgydPublished at
2023-06-07 15:35:31Event JSON
{
"id": "2fed02e20525ce080996ad40da89591840ad9cf351decc76ae778cd4b9ee6529",
"pubkey": "f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2",
"created_at": 1686152131,
"kind": 1,
"tags": [
[
"e",
"4b09126e77a8a51ac4be4a8dea5572c1d9b6eaa2dcd055866c865121a99e5723",
"",
"root"
],
[
"e",
"c6345f86404cf587a180db39917df1372011f3bbd4f9a7a8855fdf7ca5cfbb5b",
"",
"reply"
],
[
"p",
"b25e10e25d470d9b215521b50da0dfe7a209bec7fedeb53860c3e180ffdc8c11"
]
],
"content": "📅 Original date posted:2015-05-25\n📝 Original message:Very nice Emin! This could be very useful as a building block for oracle\nbased services. If only there were opcodes for working with X.509 ;)\n\nI'd suggest at least documenting in the FAQ how to extract the data from\nthe certificate:\n\nopenssl pkcs12 -in virtual-notary-cert-stocks-16070.p12 -nodes -passin\npass:\"\" | openssl x509 -text|less\n\nThat's good enough to get started, but I note two issues:\n\n\n 1. X.509 is kind of annoying to work with: example code in popular\n languages/frameworks to extract the statement would be useful.\n\n 2. The stock price plugin, at least, embeds the data as text inside the\n X.509 certificate. That's also not terribly developer friendly and risks\n parsing errors undermining security schemes built on it.\n\n The way I'd solve this is to embed either a protocol buffer or DER\n encoded structure inside the extension, so developers can extract the\n notarised data directly, without needing to do any additional parsing.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150525/eae53ab1/attachment.html\u003e",
"sig": "6d2863ee66eef8dbec7e983df7356d87b216783e6582f54b080429b1038e3d9db5c781c76442403489e6385a5402e92a927572d3040953081b23d68472e03ac1"
}