Author [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] Topic: Keyhotee ID authentication  (Read 1049 times)

0 Members and 1 Guest are viewing this topic.

Offline rysgc

  • Sr. Member
  • ****
  • Posts: 289
    • View Profile
    • DACZine.com
Keyhotee ID authentication
« on: December 20, 2013, 09:00:36 PM »

Is there any word on how authentication of users based on their Keyhotee ID would go? I'm planning on building a couple of services were users can sign in only with their Keyhotee ID. It would be great if there's an authentication api available at launch and if not I'm happy to write one which can be easily accessed by others. I understand the general authentication concepts that a browser plugin authenticates with the server , but I'm not quite sure how this translates in real life and when to expect this feature.
« Last Edit: December 20, 2013, 09:48:17 PM by GodsCreation »
DACZine.com - Receive all the latest DAC and BitShares community news straight to your inbox. Signup here or Submit news

Offline bytemaster

Re: Keyhotee ID authentication
« Reply #1 on: December 21, 2013, 08:52:24 PM »
Is there any word on how authentication of users based on their Keyhotee ID would go? I'm planning on building a couple of services were users can sign in only with their Keyhotee ID. It would be great if there's an authentication api available at launch and if not I'm happy to write one which can be easily accessed by others. I understand the general authentication concepts that a browser plugin authenticates with the server , but I'm not quite sure how this translates in real life and when to expect this feature.

We have a JSON-RPC API that you can use with Keyhotee.  I will publish some details here.
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline bytemaster

Re: Keyhotee ID authentication
« Reply #2 on: December 21, 2013, 09:00:35 PM »
method="lookup_name"
params=["bytemaster"]
result=
{
   "last_update"  : ${SECONDS_1970}
   "master_key"  : "HEX"
   "active_key"    : "HEX"
   "revoked"       : true | false
    "age"            : # of first block in which the name was registered
    "repute"        : points associated with name
    "name_hash" : "HEX 8-byte hash of name"
     "name"        : "If known, the reverse of the name_hash"
}

method = "verify_signature"
params = ["sha256 digest hex", "hex ecc compact signature" ]
result    = ["hex ECC PUBLIC KEY"]

method = "sign_message"
params = ["name", "256 digest hex" ]
result    = "hex ecc compact signature"


Server will generate a random challenge.
Client will combine the random challenge with random data and sign the result
Client will send random data + random challenge + signature + keyhotee ID to Server
Server will lookup keyhotee ID,  call verify_signature and check that the active_key == result of verify signature.

For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline rysgc

  • Sr. Member
  • ****
  • Posts: 289
    • View Profile
    • DACZine.com
Re: Keyhotee ID authentication
« Reply #3 on: December 22, 2013, 02:50:15 AM »
That's great, whenever the testing url/ip is available please do let me know.
DACZine.com - Receive all the latest DAC and BitShares community news straight to your inbox. Signup here or Submit news

Offline Troglodactyl

  • Hero Member
  • *****
  • Posts: 958
    • View Profile
Re: Keyhotee ID authentication
« Reply #4 on: December 24, 2013, 03:59:01 PM »
Are you already using the SQRL (https://www.grc.com/sqrl/sqrl.htm) interface, and if not would it be possible to do so?  That should accelerate adoption since others are already pushing it, and from my very brief investigation it looks like it should be possible.

Offline luckybit

Re: Keyhotee ID authentication
« Reply #5 on: December 25, 2013, 10:47:42 AM »
Are you already using the SQRL (https://www.grc.com/sqrl/sqrl.htm) interface, and if not would it be possible to do so?  That should accelerate adoption since others are already pushing it, and from my very brief investigation it looks like it should be possible.

I'm pushing SQRL but is it possible to use it?
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline bytemaster

Re: Keyhotee ID authentication
« Reply #6 on: December 25, 2013, 05:44:15 PM »
Are you already using the SQRL (https://www.grc.com/sqrl/sqrl.htm) interface, and if not would it be possible to do so?  That should accelerate adoption since others are already pushing it, and from my very brief investigation it looks like it should be possible.

I'm pushing SQRL but is it possible to use it?

SqRL uses a one-time key pair and assumes the private key lives on your phone.  I suspect there will be a way to combine the techniques.
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline saymasay

  • Newbie
  • *
  • Posts: 2
    • View Profile
Re: Keyhotee ID authentication
« Reply #7 on: December 29, 2013, 06:00:36 PM »
great!

 

Google+