Crypt-Sodium-XS
view release on metacpan or search on metacpan
lib/Crypt/Sodium/XS/OO/pwhash.pm view on Meta::CPAN
If this is way too long for your application, reduce memlimit, but keep
opslimit set to 3.
If the function is so fast that you can afford it to be more computationally
intensive without any usability issues, then increase opslimit.
For online use (e.g. logging in on a website), a 1 second computation is likely
to be the acceptable maximum.
For interactive use (e.g. a desktop application), a 5 second pause after having
entered a password is acceptable if the password doesnât need to be entered
more than once per session.
For non-interactive and infrequent use (e.g. restoring an encrypted backup), an
even slower computation can be an option.
However, the best defense against brute-force password cracking is to use
strong passwords.
=head1 SEE ALSO
lib/Crypt/Sodium/XS/pwhash.pm view on Meta::CPAN
If this is way too long for your application, reduce memlimit, but keep
opslimit set to 3.
If the function is so fast that you can afford it to be more computationally
intensive without any usability issues, then increase opslimit.
For online use (e.g. logging in on a website), a 1 second computation is likely
to be the acceptable maximum.
For interactive use (e.g. a desktop application), a 5 second pause after having
entered a password is acceptable if the password doesnât need to be entered
more than once per session.
For non-interactive and infrequent use (e.g. restoring an encrypted backup), an
even slower computation can be an option.
However, the best defense against brute-force password cracking is to use
strong passwords.
=head1 SEE ALSO
( run in 1.091 second using v1.01-cache-2.11-cpan-299005ec8e3 )