Home/ Questions/Q 421207
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T18:57:38+00:00

As I understand it, the best practice for generating salts is to use some

  • 0

As I understand it, the best practice for generating salts is to use some cryptic formula (or even magic constant) stored in your source code.

I’m working on a project that we plan on releasing as open source, but the problem is that with the source comes the secret formula for generating salts, and therefore the ability to run rainbow table attacks on our site.

I figure that lots of people have contemplated this problem before me, and I’m wondering what the best practice is. It seems to me that there is no point having a salt at all if the code is open source, because salts can be easily reverse-engineered.

Thoughts?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Really salts just need to be unique for each entry. Even if the attacker can calculate what the salt is, it makes the rainbow table extremely difficult to create. This is because the salt is added to the password before it is hashed, so it effectively adds to the total number of entries the rainbow table must contain to have a list of all possible values for a password field.

    • 0