Yescrypt – Scalable KDF and password hashing scheme

Re:Yescrypt – Scalable KDF and password hashing scheme by thanksforfish on Sunday August 15, 2021 @09:53AM (#28188751)

How are folks using light weight cloud resources approaching password hashing? The `10s of gigabytes of RAM` feels like an expensive requirement. Even lower memory, high iteration count sha256 seems expensive for something like AWS Lambda where you're paying by the millisecond.

From the UX perspective there's also the issue that adding a second of latency during login or registration could increase user drop off.

How many sites really incur the higher costs and higher latency?

[ Parent | on HN ]

Re:Yescrypt – Scalable KDF and password hashing scheme by forty on Sunday August 15, 2021 @10:56AM (#28189254)

You can offload some or all of the hashing to the client side. I heard this technic called "Server relief".

[ Parent | on HN ]

Re:Yescrypt – Scalable KDF and password hashing scheme by alserio on Sunday August 15, 2021 @01:08PM (#28190396)

Can you? For memory hardened algorithms you are assuming a lot of RAM from your users/clients devices

[ Parent | on HN ]

Re:Yescrypt – Scalable KDF and password hashing scheme by forty on Thursday August 19, 2021 @01:59AM (#28230821)

Yes, it certainly depends on your use case and target clients.

[ Parent | on HN ]