Yes, that's acceptable.
Le jeu. 11 oct. 2018 à 21:28, Sam Whited a écrit :
> On Thu, Oct 11, 2018, at 14:14, Thomas Bruyelle wrote:
> > That say, the downside is I have to keep both hash system, until all
> users
> > connect, which can take a long time, or can never happen!
>
> Or at least
On Thu, Oct 11, 2018, at 14:14, Thomas Bruyelle wrote:
> That say, the downside is I have to keep both hash system, until all users
> connect, which can take a long time, or can never happen!
Or at least until enough users have updated that you don't mind forcing the
rest to update their
That say, the downside is I have to keep both hash system, until all users
connect, which can take a long time, or can never happen!
Le jeu. 11 oct. 2018 à 21:08, Thomas Bruyelle a
écrit :
> This is brillant, thanks again Sam.
> I think I'll go for something like that. The argon2 hash can hold
This is brillant, thanks again Sam.
I think I'll go for something like that. The argon2 hash can hold the
version, just behind the mode, I could use that to distinguish old and new
hash.
$argon2i$*v=13*
$m=65536,t=3,p=4$SZ30vQfC522jpGssj92FkQ$xO4vPBrnd+DW/CbhiGjWW7u0s/nf7PcGUjS5bWQElYo
Le jeu.
On Thu, Oct 11, 2018, at 13:56, Thomas Bruyelle wrote:
> Unfortunately, because of that version mismatch, all my users' hashes were
> created with a version not supported by golang.org/x/crypto/argon2, so I
> can't migrate :/
I hope no problems are ever discovered in Argon2 then, it's generally
Wow indeed Sam you're completely right, with Version13 the test passes.
Thank you a lot for help.
Unfortunately, because of that version mismatch, all my users' hashes were
created with a version not supported by golang.org/x/crypto/argon2, so I
can't migrate :/
Le jeudi 11 octobre 2018
