3 ms·
I have read this several times and still don't understand the point of what you want to achieve. Some loud alarm bells ring - it looks like you're making a bran
by dalke 14y ago
I have read this several times and still don't understand the point of what you want to achieve. Some loud alarm bells ring - it looks like you're making a brand new hash algorithm. Don't every do that. Use one of the existing ones. For one, in the one you outlines, anagrams give the same hash value.
If you want everything to be client-side then you're out of luck. The client controls everything, and tweaks of the Javascript, to invert the logic of the password check, will break everything. You could have the password be the decryption key for the rest of the code to run, but I don't understand the goal.
What's the threat model? Who's is going to try to do what?
- anonymouz 14y agoI completely concur with your post, I have been scratching my head for some minutes now trying to figure out what the OP wants to do. > For one, in the one you outlines, anagrams give the same hash value It's even worse: Only the number of occurences of a given character matter for the value of the hash. So "correct horsebatterystaple" gives the same as "aabcceeeehlooprrrrsstttty". Permutation of letters does not change the output at all, making a brute force attack extremely viable.
- alhenaadams 14y agoIm trying to work within the contraint of not really having a server beyond what github pages allows while still allowing secure authentication. The goal is to end up with a js file anyone can use to have a secure login system, and has been peer reviewed and verified to work.