Re:CBCrypt: Encrypt from the client rather than send passwor...
by ybx on Tuesday October 06, 2015 @11:55AM
(#10339766)
From a usability perspective, it's probably because dealing with keys that can't just be memorized is hard for most people.
[ Parent
| on HN ]
Re:CBCrypt: Encrypt from the client rather than send passwor...
by scott_karana on Tuesday October 06, 2015 @12:39PM
(#10340142)
Can you imagine how easy it would be with browser integration, though? :-)
"The site is asking you to sign up. What secure login key would you like to use?
* Personal
* Office
* Contracting"
Re:CBCrypt: Encrypt from the client rather than send passwor...
by lsaferite on Tuesday October 06, 2015 @05:13PM
(#10342442)
Why even have those if you are, presumably, presenting yourself as the same person in each case?
You are person 'A' and you have the private key (and maybe password used to unlock the key) to prove this fact.
You don't need different private keys for each and the remote end just has a public key that says the account belongs to person 'A' and that key is public.
Re:CBCrypt: Encrypt from the client rather than send passwor...
by scott_karana on Tuesday October 06, 2015 @05:55PM
(#10342689)
I guess you're right. :-)
The only usage case would be if someone wanted multiple accounts at the same site, and that would be rare indeed.
The only other real concern, site hacks/collaboration leaking where you're a member of by public key, wouldn't be alleviated by merely a handful of keys anyways: you'd need unique keypairs for each to be truly secure.
Re:CBCrypt: Encrypt from the client rather than send passwor...
by eximius on Tuesday October 06, 2015 @01:36PM
(#10340709)
This is what I am planning for a project of mine called AutoAuth. It's put on hold cause I have no idea how to write Chrome extensions.