Egor Homakov

>I think you need to address two audiences: I think we don't need to communicate to average users at this stage. It's harder. Unlike pw managers, we need **admins** and...

Missed this issue @kotodharma can you look at https://sakurity.github.io/securelogin-spec/index.html is it close enough?

Pretty much every post about SL mentions it is deterministic KDF, i.e. private key is generated from scrypt(email, pw), to recover/transfer you just use the same inputs, and there's nothing...

Everything is prone to bruteforce at some extent. Some creds are hidden behind central authorities and have rate limiting, but it is even worse. We use sufficiently strong derivation to...

All user supplies is email and pw, which are used as scrypt(email+pw). No other seed is used. The attacker may test a lot of email+pw combinations but given derivation scheme...

> site breach will leak all keys and allow an attacker the pleasure of picking off weak passwords in bulk. Once again: site breach is not an "if", public key...

@steph643 Theirs (SQRL) approach as far as I understand is: >The Identity Master Key is always stored in encrypted form under the user's chosen (and readily changeable) authentication password. This...

>If you wish an example of crime made possible by such a weakness look up Deterministic Bitcoin Wallets etc. Brainwallets are amazing if done right. Separate post to distinguish bad...

I see, then you should also drop QR part of the name, a bit frustrating. Anyway, it's just different vision, also better than what we have now.

I understand why - I also want to put QR back for doublesign or untrusted devices, but at this step with low adaption, imo no need to bloat software with...