@jedisct1 @ParagonIE Right now, libsodium uses a fork of my old development tree (escrypt from 2013). I guess it'll switch to yescrypt?
-
-
-
@solardiz@ParagonIE Very likely, yes. Although the high-level pwhash() API will use Argon2. - 3 more replies
New conversation -
-
-
@jedisct1@ParagonIE Good advice for projects that are built from scratch in 2016. One may need compatibility layer for existing hashes. -
@brutemorse@jedisct1 We're adding an FAQ entry about migrating legacy hashes at the moment. - 1 more reply
New conversation -
-
-
@jedisct1@ParagonIE JFYI, I expect to release yescrypt 1.0 this year - same hashes as final PHC submission, but finalized encoding & APIThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@jedisct1@ParagonIE Hash comparison in Ruby with == ?
New conversation -
-
-
-
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.