Except brute forcing the login panel of course but you can always limit login attempts.
An example for ‘custom encryption’ might be something I wrote for a school project when I was 14.
Algorithm was like this: 1. Get user’s password as $passwd 2. Use MD5 encryption on $passwd 3. Substr and remove a certain amount of characters from MD5 string. 4. Use MD5 on that string twice more and remove 2 chars from the end. 5. Store the result string in the database as user’s password
You can mix and match this however you’d like. You can even use the user’s registration timestamp or username length as key while encrypting so it’s not the same algorithm for every single user.
And do the same control when a user is logging in.
I can’t be the only one who have thought of this. So why isn’t this more common? It’s basically unbreakable, and since there’s a shit ton of websites/apps that are being hacked and release our one-time-encrypted passwords into the wild every single day, it just makes sense to me.
submitted by /u/33sikici33
[link] [comments]