Closed friedkeenan closed 5 years ago
Nope, I only chose MD5 because it was easy to implement. In reality, it's a terrible choice and I'd jump at the opportunity to use stronger cryptography. :)
Does libnx have native hashing functions now?
EDIT: Just noticed your commit. Nice work, especially for catching that little oversight on my part.
Yep, hardware accelerated and everything: https://switchbrew.github.io/libnx/dir_2874fbf892ad5b8020be2442f929b820.html
It's what I used for the hashing commands I added
If you want, I can work on this later or tomorrow (should be relatively simple to add)
Fixed with c88819edc4f2f083e450a676a8892bc73d34f82d
Now that libnx has hardware accelerated crypto stuff, including sha256, I think it makes more sense to use sha256 for the password checking. Though, it wouldn't make too much of a difference since to find out the hash of the password, you'd have to have a level of access that means an attacker could already have done nasty stuff to your Switch.
I'm just making this issue to make sure there's no reason @Cesura specifically used MD5