Password Hashing

[elusiveshiba]

Currently the master password entered during setup is passed to the backend without hashing.

Should this be hashed? If so, when and how?

[edtubbs]

Yes we should hash it right after receipt from frontend. Using something like Argon2id in DKM or another password hashing algorithm.

[SomeoneWeird]

Yeah we already do this - I think @elusiveshiba is specifically questioning if we should be hashing in the frontend in ADDITION to the backend. There many pros and cons to this so I think it needs a lot of discussion before we make any changes.

[edtubbs]

Understood. It should be possible to do a lightweight hash in the frontend. It's a local interface on the network right now so might not be necessary, but it would be an issue if it's accessible in the clear over a remote connection.

[DivineGod]

I would rather support https instead

front-end hashing doesn’t really add much security at all

[elusiveshiba]

Yeah we already do this - I think @elusiveshiba is specifically questioning if we should be hashing in the frontend in ADDITION to the backend. There many pros and cons to this so I think it needs a lot of discussion before we make any changes.

Yep that's it, I'm flagging that there's currently a step where the password is communicated by the frontend, to the backend, unhashed/unencrypted.
I like @DivineGod 's suggestion