Login service computes password hashes on a single thread #46
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I was kind of lazy and implemented password hashing directly in the database, which is single-threaded. Argon2 is a really compute-heavy hash function so we should probably compute it asynchronously and offload it to multiple cores. (Preferably remove the need for it completely, we could use session tokens which are not as hard to compute...)