{"type":"rich","version":"1.0","author_name":"npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgyd","author_url":"https://nostr.ae/npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgyd","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2014-04-04\n📝 Original message:This comes up every few months. I think the problem you are trying to solve\nis already solved by SSL client certificates, and if you want to help make\nthem more widespread the programs you need to upgrade are web browsers and\nnot Bitcoin wallets. There are certainly bits of infrastructure you could\nreuse here and there, like perhaps a TREZOR with a custom firmware\nextension for really advanced/keen users, but overall Bitcoin and website\nauthentication are unrelated problems.\n\n\nOn Fri, Apr 4, 2014 at 2:15 PM, Eric Larchevêque \u003celarch at gmail.com\u003e wrote:\n\n\u003e Hello,\n\u003e\n\u003e I've written a draft BIP description of an authentication protocol based\n\u003e on Bitcoin public address.\n\u003e\n\u003e By authentication we mean to prove to a service/application that we\n\u003e control a specific Bitcoin address by signing a challenge, and that all\n\u003e related data and settings may securely be linked to our session.\n\u003e\n\u003e The aim is to greatly facilitate sign ups and logins to services and\n\u003e applications, improving the Bitcoin ecosystem as a whole.\n\u003e\n\u003e https://github.com/bitid/bitid/blob/master/BIP_draft.md\n\u003e\n\u003e Demo website :\n\u003e http://bitid-demo.herokuapp.com/\n\u003e\n\u003e Classical password authentication is an insecure process that could be\n\u003e solved with public key cryptography. The problem is that it theoretically\n\u003e offloads a lot of complexity and responsibility on the user. Managing\n\u003e private keys securely is complex. However this complexity is already being\n\u003e addressed in the Bitcoin ecosystem. So doing public key authentication is\n\u003e practically a free lunch to bitcoiners.\n\u003e\n\u003e I've formatted the protocol description as a BIP because this is the only\n\u003e way to have all major wallets implementing it, and because it completely\n\u003e fits in my opinion the BIP \"process\" category.\n\u003e\n\u003e Please read it and let me know your thoughts and comments so we can\n\u003e improve on this draft.\n\u003e\n\u003e Eric Larcheveque\n\u003e elarch at gmail.com\n\u003e\n\u003e\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e\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\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140404/99be34a9/attachment.html\u003e"}