Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider switching to libsodium for encryption #86

Open
rfl890 opened this issue Apr 4, 2024 · 7 comments
Open

Consider switching to libsodium for encryption #86

rfl890 opened this issue Apr 4, 2024 · 7 comments

Comments

@rfl890
Copy link

rfl890 commented Apr 4, 2024

Rolling your own crypto is never good.

@waterflow1337
Copy link

« lol » ?

@rfl890
Copy link
Author

rfl890 commented Apr 7, 2024

He hardcoded the salt in the password hash

@GuardianN06
Copy link

is that a bad thing?

@Tr3yWay996
Copy link

is that a bad thing?

The "salt" is what hashes your thing i think but if its bad tho ? idk

@rfl890
Copy link
Author

rfl890 commented Oct 28, 2024

Well, consider the following scenario. An attacker compromises a multitude of PCs and obtains a list of password hashes. If the salt was randomized for each hash, then the attacker would need to brute-force each password hash individually. But since the salt is hard-coded, the attacker would be able to compare the passwords to one list of common passwords, lowering the amount of work he would need to do to crack the passwords.

@jaypaw549
Copy link

To be more accurate, he would be able to pre-compile a list of hashed passwords with that salt, and then any weak passwords could just be looked up. It's called a rainbow table attack.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants