Nice. Did you measure the performance of scrypt.js? The PBKDF2 implementation in Python and both Chrome/Firefox are similar for me and the Python documentation states something like 3x slower that the OpenSSL implementation [1]. So it sounds pretty usable to strengthen the password while still being usable.
Nice. I guess the big difference is the key used for the symmetric encryption. I'm using PBKDF2 to derive the final key to make it harder to brute force in case you get the HTML file.
It took way too long on my laptop (i5-6200U).
With a decent random password (say, 14 letters), the search space will be very large.
If a determined attacker (with a couple of GPUs) can attempt 100.000 passwords per second it will still be impossible to crack in an acceptable time.
If we assume that this determined attacker is calculating these hashes 100.000 faster than the average browser, it should be enough if the user has to wait for one second, not one minute.
On the other hand everyone has different security requirements so perhaps making it configurable is the best way to go proceed (with some recommendations).
Indeed. The project motivation is even similar to mine (bootstrap yourself in case everything gets lost). I guess the main difference between the two is that I tried to make the generated HTML minimal so it's easier to verify before entering a password.
[+] [-] aurorabbit|6 years ago|reply
It offers scrypt + aes-gcm, encoded into 256 emoji; all the crypto is in https://github.com/aurorabbit/libemojicrypt/blob/master/prot... (I could have went without a subrepo, but in theory it makes non-web integration or alternate interfaces simple.)
It's based off of ricmoo's scrypt.js, pfrazee's base-emoji, and WebCrypto.
Output contains a header (with N/r parameters), salt, IV, and HMAC. Room for a dozen more protocol versions as well.
It's abandoned, looking for a loving home! Work for some new (and some unimplemented) features is laid out here: https://github.com/aurorabbit/emojicrypt.com/issues
[+] [-] dividuum|6 years ago|reply
[1] https://docs.python.org/3/library/hashlib.html#hashlib.pbkdf...
[+] [-] aurorabbit|6 years ago|reply
[+] [-] unknown|6 years ago|reply
[deleted]
[+] [-] camsjams|6 years ago|reply
With a slight difference, it works 100% in the browser, you can use it here: https://camsjams.github.io/mr-roboto/
But you need to store the output somewhere safe.
[+] [-] dividuum|6 years ago|reply
[+] [-] maxlaumeister|6 years ago|reply
https://www.maxlaumeister.com/pagecrypt/
Mine was originally in-browser, but thanks to some contributors (Zoltán Gálli and Nial Francis) it has Python and PowerShell CLIs now.
I like your use of async to make sure the work stays off the main thread.
[+] [-] Tepix|6 years ago|reply
[+] [-] Tepix|6 years ago|reply
If we assume that this determined attacker is calculating these hashes 100.000 faster than the average browser, it should be enough if the user has to wait for one second, not one minute.
On the other hand everyone has different security requirements so perhaps making it configurable is the best way to go proceed (with some recommendations).
PS according to https://github.com/analsec/hashcatbenchmark/blob/master/Nvid... a RTX 2080Ti can crack 750k WPA-EAPOL-PBKDF2 with 4096 rounds per second.
[+] [-] sowbug|6 years ago|reply
[+] [-] dividuum|6 years ago|reply
[+] [-] eitland|6 years ago|reply
[+] [-] dividuum|6 years ago|reply
[+] [-] bmsleight_|6 years ago|reply
[+] [-] dividuum|6 years ago|reply