How should I really save salts
I have done a lot of research on security, and password hashing, but there is one thing that there seems to be a lot of opinions about. How to save salts. I was hoping someone with expertise in this field could give a professional opinion on the matter. Should I store salts in the DB? In a separate file? Should they be in the same DB as the passwords?
Thanks for the help.
javascript hash
edited Nov 25 '18 at 20:25
Neil Lunn
99.1k23175184
asked Nov 25 '18 at 19:48
Brandon FederBrandon Feder
114
add a comment |
I have done a lot of research on security, and password hashing, but there is one thing that there seems to be a lot of opinions about. How to save salts. I was hoping someone with expertise in this field could give a professional opinion on the matter. Should I store salts in the DB? In a separate file? Should they be in the same DB as the passwords?
Thanks for the help.
javascript hash
edited Nov 25 '18 at 20:25
Neil Lunn
99.1k23175184
asked Nov 25 '18 at 19:48
Brandon FederBrandon Feder
114
The first rule to password security is, don’t roll your own encryption algorithm. Use a tried and true library like bcrypt.
– Nate
Nov 25 '18 at 19:53
1
You might want to look into bcrypt, which as far as I know, uses random salts and manage them in a way I can't actually explain it. But yes, it does save these salts for you without having to export it to files, etc.
– ionizer
Nov 25 '18 at 19:53
add a comment |
I have done a lot of research on security, and password hashing, but there is one thing that there seems to be a lot of opinions about. How to save salts. I was hoping someone with expertise in this field could give a professional opinion on the matter. Should I store salts in the DB? In a separate file? Should they be in the same DB as the passwords?
Thanks for the help.
javascript hash
edited Nov 25 '18 at 20:25
Neil Lunn
99.1k23175184
asked Nov 25 '18 at 19:48
Brandon FederBrandon Feder
114
I have done a lot of research on security, and password hashing, but there is one thing that there seems to be a lot of opinions about. How to save salts. I was hoping someone with expertise in this field could give a professional opinion on the matter. Should I store salts in the DB? In a separate file? Should they be in the same DB as the passwords?
Thanks for the help.
javascript hash
javascript hash
edited Nov 25 '18 at 20:25
Neil Lunn
99.1k23175184
asked Nov 25 '18 at 19:48
Brandon FederBrandon Feder
114
edited Nov 25 '18 at 20:25
Neil Lunn
99.1k23175184
asked Nov 25 '18 at 19:48
Brandon FederBrandon Feder
114
edited Nov 25 '18 at 20:25
Neil Lunn
99.1k23175184
edited Nov 25 '18 at 20:25
Neil Lunn
99.1k23175184
edited Nov 25 '18 at 20:25
Neil Lunn
99.1k23175184
99.1k23175184
asked Nov 25 '18 at 19:48
Brandon FederBrandon Feder
114
asked Nov 25 '18 at 19:48
Brandon FederBrandon Feder
114
asked Nov 25 '18 at 19:48
Brandon FederBrandon Feder
114
114
The first rule to password security is, don’t roll your own encryption algorithm. Use a tried and true library like bcrypt.
– Nate
Nov 25 '18 at 19:53
1
You might want to look into bcrypt, which as far as I know, uses random salts and manage them in a way I can't actually explain it. But yes, it does save these salts for you without having to export it to files, etc.
– ionizer
Nov 25 '18 at 19:53
add a comment |
The first rule to password security is, don’t roll your own encryption algorithm. Use a tried and true library like bcrypt.
– Nate
Nov 25 '18 at 19:53
1
You might want to look into bcrypt, which as far as I know, uses random salts and manage them in a way I can't actually explain it. But yes, it does save these salts for you without having to export it to files, etc.
– ionizer
Nov 25 '18 at 19:53
The first rule to password security is, don’t roll your own encryption algorithm. Use a tried and true library like bcrypt.
– Nate
Nov 25 '18 at 19:53
The first rule to password security is, don’t roll your own encryption algorithm. Use a tried and true library like bcrypt.
– Nate
Nov 25 '18 at 19:53
1
1
You might want to look into bcrypt, which as far as I know, uses random salts and manage them in a way I can't actually explain it. But yes, it does save these salts for you without having to export it to files, etc.
– ionizer
Nov 25 '18 at 19:53
You might want to look into bcrypt, which as far as I know, uses random salts and manage them in a way I can't actually explain it. But yes, it does save these salts for you without having to export it to files, etc.
– ionizer
Nov 25 '18 at 19:53
add a comment |
2 Answers
2
active
oldest
votes
@ManyelReyes has the correct answer, and here is why:
Salts protect against rainbow tables. A rainbow table is a precalculated list of the hashes of common passwords.
So, if you just saved the password hash for someone and they used a common password, then the attacker could find it in the rainbow table and know the password.
By adding something random to every password you make rainbow tables not work. They work because they can be precalculated. When you add the salt into the user's password the rainbow table can't be precalcuated, since the salt is random. If you used the same salt for every user they could make a rainbow table using that salt.
Since it does not change the security provided by salts to have the attacker know that you are using them and what the salt is, you can store the salt in the clear in the user table. (I've also appended them to the hash result, then I don't need an extra column, as long as the hash is always the same length.)
answered Nov 25 '18 at 20:24
HoganHogan
55.3k966103
add a comment |
There should be one random salt per user (Do not use the same salt to every user). Every time a user creates an account or changes their password, the password should be hashed using a new random salt. The salt should be stored in the user account table alongside the hash.
Add the salt to the password and hash it with a standard password hashing function. Save both the salt and the hash in the user's database record.
To validate a password, retrieve the user's salt and hash from the database. Add the salt to the given password and hash it using the same hash function.
Compare the hash of the given password with the hash from the database. If they match, the password is correct. Otherwise, the password is incorrect.
More info here
answered Nov 25 '18 at 20:15
Manuel ReyesManuel Reyes
616
How do you know which user you should get the hash for?
– Brandon Feder
Nov 28 '18 at 23:36
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53471249%2fhow-should-i-really-save-salts%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
@ManyelReyes has the correct answer, and here is why:
Salts protect against rainbow tables. A rainbow table is a precalculated list of the hashes of common passwords.
So, if you just saved the password hash for someone and they used a common password, then the attacker could find it in the rainbow table and know the password.
By adding something random to every password you make rainbow tables not work. They work because they can be precalculated. When you add the salt into the user's password the rainbow table can't be precalcuated, since the salt is random. If you used the same salt for every user they could make a rainbow table using that salt.
Since it does not change the security provided by salts to have the attacker know that you are using them and what the salt is, you can store the salt in the clear in the user table. (I've also appended them to the hash result, then I don't need an extra column, as long as the hash is always the same length.)
answered Nov 25 '18 at 20:24
HoganHogan
55.3k966103
add a comment |
@ManyelReyes has the correct answer, and here is why:
Salts protect against rainbow tables. A rainbow table is a precalculated list of the hashes of common passwords.
So, if you just saved the password hash for someone and they used a common password, then the attacker could find it in the rainbow table and know the password.
By adding something random to every password you make rainbow tables not work. They work because they can be precalculated. When you add the salt into the user's password the rainbow table can't be precalcuated, since the salt is random. If you used the same salt for every user they could make a rainbow table using that salt.
Since it does not change the security provided by salts to have the attacker know that you are using them and what the salt is, you can store the salt in the clear in the user table. (I've also appended them to the hash result, then I don't need an extra column, as long as the hash is always the same length.)
answered Nov 25 '18 at 20:24
HoganHogan
55.3k966103
add a comment |
@ManyelReyes has the correct answer, and here is why:
Salts protect against rainbow tables. A rainbow table is a precalculated list of the hashes of common passwords.
So, if you just saved the password hash for someone and they used a common password, then the attacker could find it in the rainbow table and know the password.
By adding something random to every password you make rainbow tables not work. They work because they can be precalculated. When you add the salt into the user's password the rainbow table can't be precalcuated, since the salt is random. If you used the same salt for every user they could make a rainbow table using that salt.
Since it does not change the security provided by salts to have the attacker know that you are using them and what the salt is, you can store the salt in the clear in the user table. (I've also appended them to the hash result, then I don't need an extra column, as long as the hash is always the same length.)
answered Nov 25 '18 at 20:24
HoganHogan
55.3k966103
@ManyelReyes has the correct answer, and here is why:
Salts protect against rainbow tables. A rainbow table is a precalculated list of the hashes of common passwords.
So, if you just saved the password hash for someone and they used a common password, then the attacker could find it in the rainbow table and know the password.
By adding something random to every password you make rainbow tables not work. They work because they can be precalculated. When you add the salt into the user's password the rainbow table can't be precalcuated, since the salt is random. If you used the same salt for every user they could make a rainbow table using that salt.
Since it does not change the security provided by salts to have the attacker know that you are using them and what the salt is, you can store the salt in the clear in the user table. (I've also appended them to the hash result, then I don't need an extra column, as long as the hash is always the same length.)
answered Nov 25 '18 at 20:24
HoganHogan
55.3k966103
answered Nov 25 '18 at 20:24
HoganHogan
55.3k966103
answered Nov 25 '18 at 20:24
HoganHogan
55.3k966103
answered Nov 25 '18 at 20:24
HoganHogan
55.3k966103
55.3k966103
add a comment |
add a comment |
There should be one random salt per user (Do not use the same salt to every user). Every time a user creates an account or changes their password, the password should be hashed using a new random salt. The salt should be stored in the user account table alongside the hash.
Add the salt to the password and hash it with a standard password hashing function. Save both the salt and the hash in the user's database record.
To validate a password, retrieve the user's salt and hash from the database. Add the salt to the given password and hash it using the same hash function.
Compare the hash of the given password with the hash from the database. If they match, the password is correct. Otherwise, the password is incorrect.
More info here
answered Nov 25 '18 at 20:15
Manuel ReyesManuel Reyes
616
How do you know which user you should get the hash for?
– Brandon Feder
Nov 28 '18 at 23:36
add a comment |
There should be one random salt per user (Do not use the same salt to every user). Every time a user creates an account or changes their password, the password should be hashed using a new random salt. The salt should be stored in the user account table alongside the hash.
Add the salt to the password and hash it with a standard password hashing function. Save both the salt and the hash in the user's database record.
To validate a password, retrieve the user's salt and hash from the database. Add the salt to the given password and hash it using the same hash function.
Compare the hash of the given password with the hash from the database. If they match, the password is correct. Otherwise, the password is incorrect.
More info here
answered Nov 25 '18 at 20:15
Manuel ReyesManuel Reyes
616
How do you know which user you should get the hash for?
– Brandon Feder
Nov 28 '18 at 23:36
add a comment |
There should be one random salt per user (Do not use the same salt to every user). Every time a user creates an account or changes their password, the password should be hashed using a new random salt. The salt should be stored in the user account table alongside the hash.
Add the salt to the password and hash it with a standard password hashing function. Save both the salt and the hash in the user's database record.
To validate a password, retrieve the user's salt and hash from the database. Add the salt to the given password and hash it using the same hash function.
Compare the hash of the given password with the hash from the database. If they match, the password is correct. Otherwise, the password is incorrect.
More info here
answered Nov 25 '18 at 20:15
Manuel ReyesManuel Reyes
616
There should be one random salt per user (Do not use the same salt to every user). Every time a user creates an account or changes their password, the password should be hashed using a new random salt. The salt should be stored in the user account table alongside the hash.
Add the salt to the password and hash it with a standard password hashing function. Save both the salt and the hash in the user's database record.
To validate a password, retrieve the user's salt and hash from the database. Add the salt to the given password and hash it using the same hash function.
Compare the hash of the given password with the hash from the database. If they match, the password is correct. Otherwise, the password is incorrect.
More info here
answered Nov 25 '18 at 20:15
Manuel ReyesManuel Reyes
616
answered Nov 25 '18 at 20:15
Manuel ReyesManuel Reyes
616
answered Nov 25 '18 at 20:15
Manuel ReyesManuel Reyes
616
answered Nov 25 '18 at 20:15
Manuel ReyesManuel Reyes
616
616
How do you know which user you should get the hash for?
– Brandon Feder
Nov 28 '18 at 23:36
add a comment |
How do you know which user you should get the hash for?
– Brandon Feder
Nov 28 '18 at 23:36
How do you know which user you should get the hash for?
– Brandon Feder
Nov 28 '18 at 23:36
How do you know which user you should get the hash for?
– Brandon Feder
Nov 28 '18 at 23:36
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53471249%2fhow-should-i-really-save-salts%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
The first rule to password security is, don’t roll your own encryption algorithm. Use a tried and true library like bcrypt.
– Nate
Nov 25 '18 at 19:53
1
You might want to look into bcrypt, which as far as I know, uses random salts and manage them in a way I can't actually explain it. But yes, it does save these salts for you without having to export it to files, etc.
– ionizer
Nov 25 '18 at 19:53