📅 Original date posted:2013-08-09
📝 Original message:On 9 August 2013 13:59, Wendell <w at grabhive.com> wrote:
> We have been discussing something like this over here too, as well as
> exploring more esoteric blockchain+signature-based "SSO" implementations as
> discussed by John Light and others.
>
I've been using SSO for years using an X.509 private key in my browser, and
my public key referenced in my home page.
The unfortunate thing is that X.509 tends to use RSA, and bitcoin tends to
use ECC for space reasons. Since, in its simplest form, bitcoin is a
distributed ledger of public key / balance values you could imagine an
enormous eco system where every key pair become a wallet with 10s of
millions of users.
I was thinking about an alt coin along these lines. The problem is that
there's no OP_CODE for RSA and the block chain would become massive.
>
> One of our long-term ambitions with Hive is to provide a (mostly)
> user-transparent, decentralized authentication service. It sounds like our
> infrastructure could already handle a Persona implementation, and we very
> much want to get behind some forward-thinking standard. So as long as the
> plan _IS_ to remove said 'centralized struts' at the appropriate time, I'd
> say we're interested in exploring this further.
>
Sounds great, would love to hear more about what you come up with!
>
> -wendell
>
> grabhive.com | twitter.com/grabhive | gpg: 6C0C9411
>
> On Aug 9, 2013, at 1:43 PM, Mike Hearn wrote:
>
> > This is just me making notes for myself, I'm not seriously suggesting
> this be implemented any time soon.
> >
> > Mozilla Persona is an infrastructure for web based single sign on. It
> works by having email providers sign temporary certificates for their
> users, whose browsers then sign server-provided challenges to prove their
> email address.
> >
> > Because an SSO system is a classic chicken/egg setup, they run various
> fallback services that allow anyone with an email address to take part.
> They also integrate with the Google/Yahoo SSO systems as well. The
> intention being that they do this until Persona becomes big enough to
> matter, and then they can remove the centralised struts and the system
> becomes transparently decentralised.
> >
> > In other words, they seem to do a lot of things right.
> >
> > Of course you can already sign payments using an X.509 cert issued to an
> email address with v1 of the payment protocol, so technically no new PKI is
> needed. But the benefit of leveraging Persona would be convenience - you
> can get yourself a Persona cert and use it to sign in to websites with a
> single click, and the user experience is smart and professional. CAs in
> contrast are designed for web site admins really so the experience of
> getting a cert for an email address is rather variable and more heavyweight.
> >
> > Unfortunately Persona does not use X.509. It uses a custom thing based
> on JSON. However, under the hood it's just assertions signed by RSA keys,
> so an implementation is likely to be quite easy. From the users
> perspective, their wallet app would embed a browser and drive it as if it
> were signing into a website, but stop after the user is signed into Persona
> and a user cert has been provisioned. It can then sign payment requests
> automatically. For many users, it'd be just one click, which is pretty neat.
>
>
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20130809/f309fcc6/attachment.html>;
Melvin Carvalho [ARCHIVE] /
npub1uv…saxrt
2023-06-07 15:05:46
in reply to nevent1q…j34x
Author Public Key
npub1uvtfvcegcn9kds68r8he57emc480vqtx8t22kpsctxgjxae44gvsksaxrtPublished at
2023-06-07 15:05:46Event JSON
{
"id": "a677a59c367047efae993523a530a48ff30a0c5aadb3767555a21202ff046caa",
"pubkey": "e316966328c4cb66c34719ef9a7b3bc54ef601663ad4ab06185991237735aa19",
"created_at": 1686150346,
"kind": 1,
"tags": [
[
"e",
"f3ae186e8223c167a44d4fe5fb8d14e50a311a37a9b6f42f94ba5c3fade227a9",
"",
"root"
],
[
"e",
"5e0ff68e153e9166c8c2e9ced5e9c6c60db59b398ecfdf421a64e53a78e4d715",
"",
"reply"
],
[
"p",
"c534bb535ca1eba460ab96ad869cfa2160259b441c95515f281c187f0130f4f3"
]
],
"content": "📅 Original date posted:2013-08-09\n📝 Original message:On 9 August 2013 13:59, Wendell \u003cw at grabhive.com\u003e wrote:\n\n\u003e We have been discussing something like this over here too, as well as\n\u003e exploring more esoteric blockchain+signature-based \"SSO\" implementations as\n\u003e discussed by John Light and others.\n\u003e\n\nI've been using SSO for years using an X.509 private key in my browser, and\nmy public key referenced in my home page.\n\nThe unfortunate thing is that X.509 tends to use RSA, and bitcoin tends to\nuse ECC for space reasons. Since, in its simplest form, bitcoin is a\ndistributed ledger of public key / balance values you could imagine an\nenormous eco system where every key pair become a wallet with 10s of\nmillions of users.\n\nI was thinking about an alt coin along these lines. The problem is that\nthere's no OP_CODE for RSA and the block chain would become massive.\n\n\n\u003e\n\u003e One of our long-term ambitions with Hive is to provide a (mostly)\n\u003e user-transparent, decentralized authentication service. It sounds like our\n\u003e infrastructure could already handle a Persona implementation, and we very\n\u003e much want to get behind some forward-thinking standard. So as long as the\n\u003e plan _IS_ to remove said 'centralized struts' at the appropriate time, I'd\n\u003e say we're interested in exploring this further.\n\u003e\n\nSounds great, would love to hear more about what you come up with!\n\n\n\u003e\n\u003e -wendell\n\u003e\n\u003e grabhive.com | twitter.com/grabhive | gpg: 6C0C9411\n\u003e\n\u003e On Aug 9, 2013, at 1:43 PM, Mike Hearn wrote:\n\u003e\n\u003e \u003e This is just me making notes for myself, I'm not seriously suggesting\n\u003e this be implemented any time soon.\n\u003e \u003e\n\u003e \u003e Mozilla Persona is an infrastructure for web based single sign on. It\n\u003e works by having email providers sign temporary certificates for their\n\u003e users, whose browsers then sign server-provided challenges to prove their\n\u003e email address.\n\u003e \u003e\n\u003e \u003e Because an SSO system is a classic chicken/egg setup, they run various\n\u003e fallback services that allow anyone with an email address to take part.\n\u003e They also integrate with the Google/Yahoo SSO systems as well. The\n\u003e intention being that they do this until Persona becomes big enough to\n\u003e matter, and then they can remove the centralised struts and the system\n\u003e becomes transparently decentralised.\n\u003e \u003e\n\u003e \u003e In other words, they seem to do a lot of things right.\n\u003e \u003e\n\u003e \u003e Of course you can already sign payments using an X.509 cert issued to an\n\u003e email address with v1 of the payment protocol, so technically no new PKI is\n\u003e needed. But the benefit of leveraging Persona would be convenience - you\n\u003e can get yourself a Persona cert and use it to sign in to websites with a\n\u003e single click, and the user experience is smart and professional. CAs in\n\u003e contrast are designed for web site admins really so the experience of\n\u003e getting a cert for an email address is rather variable and more heavyweight.\n\u003e \u003e\n\u003e \u003e Unfortunately Persona does not use X.509. It uses a custom thing based\n\u003e on JSON. However, under the hood it's just assertions signed by RSA keys,\n\u003e so an implementation is likely to be quite easy. From the users\n\u003e perspective, their wallet app would embed a browser and drive it as if it\n\u003e were signing into a website, but stop after the user is signed into Persona\n\u003e and a user cert has been provisioned. It can then sign payment requests\n\u003e automatically. For many users, it'd be just one click, which is pretty neat.\n\u003e\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e Get 100% visibility into Java/.NET code with AppDynamics Lite!\n\u003e It's a free troubleshooting tool designed for production.\n\u003e Get down to code-level detail for bottlenecks, with \u003c2% overhead.\n\u003e Download for free and get started troubleshooting in minutes.\n\u003e http://pubads.g.doubleclick.net/gampad/clk?id=48897031\u0026iu=/4140/ostg.clktrk\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20130809/f309fcc6/attachment.html\u003e",
"sig": "6cfe09f29c000dcad03717baa7bc3a4add5fa12e03249e172676d0a01ea58226c4ea25737ef2be8959b6da1713fde30ed9ef52937c40628c06c3e2598542f16e"
}