Skip to main content
OverflowAI is here! AI power for your Stack Overflow for Teams knowledge community. Learn more

New answers tagged

2 votes

Is this idea for secure password storage a good one?

the amount of characters added is different for each user! [...] This relies on two things, however, the hashing algorithm is kept secret, That's all anyone needs to know to see that this is a bad ...
Tom's user avatar
  • 10.4k
4 votes

Is this idea for secure password storage a good one?

If you are doing the hashing and padding on the client side then how can you keep your algorithm secret. Considering you try to obfuscate your code, still it can be de-obfuscated easily by someone who ...
und3rh00ds's user avatar
0 votes

Is it safe to derive the salt from the users email/phone number when pre-hashing a password to be sent to a server?

In order to make an encryption key out of a password you'll need a slow key derivation function made for passwords, such as scrypt, bcrypt, argon2, etc. root_key = slow_kdf(password, salt_1) Then you ...
n-l-i's user avatar
  • 216
-2 votes

Is it safe to derive the salt from the users email/phone number when pre-hashing a password to be sent to a server?

The primary point of using a salt is to make sure that your passwords don’t match other people’s passwords. Many people use 123456 as a password. Without salt, they all have the same hash. Lots of ...
gnasher729's user avatar
  • 2,395
0 votes
Accepted

Is it safe to derive the salt from the users email/phone number when pre-hashing a password to be sent to a server?

It means that if the communications is logged or intercepted the salt can be intercepted, any other user could look to see the method and since it is client side you might presume the hash method ...
Willtech's user avatar
  • 124
0 votes

Is it safe to derive the salt from the users email/phone number when pre-hashing a password to be sent to a server?

So my idea was to derive the salt from the email using a KDF. In theory, this makes it possible for attackers to precompute the salt, and precompute many hashes, and use those to quickly brute-force ...
Sjoerd's user avatar
  • 30.8k
0 votes

Is it safe to derive the salt from the users email/phone number when pre-hashing a password to be sent to a server?

Since your users send unencrypted data to the server, server sees unencrypted data before encrypting them and storing. Thus, "If a malicious actor ... wanted to access the customer data", ...
mentallurg's user avatar
  • 12.4k
57 votes
Accepted

Is this idea for secure password storage a good one?

You recently asked about "security by obscurity". This is that. A very complicated process that fails once it is known. And if the database of hashes gets leaked, from one server, why do you ...
schroeder's user avatar
  • 130k
19 votes

Is this idea for secure password storage a good one?

Leaving aside some of the technical implementation issues (how you're generating the "random" characters, how your servers communicate to work out how many they need to strip off each side, ...
Gh0stFish's user avatar
  • 11.7k
9 votes

How to track PBKDF2 progress?

Messing around with cryptographic code just to get a more accurate progress bar to display to users on a login seems like a very dangerous idea for limited benefits. It's very easy to introduce subtle ...
Gh0stFish's user avatar
  • 11.7k
22 votes
Accepted

How to track PBKDF2 progress?

If your PBKDF2 calculations take so long that you need a progress bar, there's something seriously wrong. The calculations shouldn't take more than a few seconds, otherwise the number of iterations is ...
Ja1024's user avatar
  • 7,387
0 votes

How to track PBKDF2 progress?

PBKDF2 does a number of iterations. The correct way to track progress is to add some code to the loop that reports the current iteration number. If your current crypto implementation does not support ...
Sjoerd's user avatar
  • 30.8k
4 votes
Accepted

How do databases/companies change their hashing algorithm?

The application does not have to and should not wait until the user has logged in. They can hash all currently stored hashes with the new algorithm to produce h2(h1(p)), where h1 is the old algorithm ...
Ja1024's user avatar
  • 7,387
3 votes

How do databases/companies change their hashing algorithm?

You answered your own question - your second hypotheses is correct, this is how it's done in practice. Notice that the password hashing function built-in to most frameworks is actually designed with ...
mti2935's user avatar
  • 23.6k
2 votes
Accepted

Is there anyway to crack this salted Hash?

This one is an LM:NTLM hash pair, how Windows stores them (the SAM). They're the "same" password, stored two different ways: You can crack the first half as LM (hashcat mode 3000, case-...
Royce Williams's user avatar
5 votes
Accepted

Why does OWASP recommend only 1 degree of parallelism for Argon2id

The recommendation was introduced with a commit which references a GitHub comment. In that comment, the author gives the following reason for recommending a parallelism of 1: For authentication you ...
Ja1024's user avatar
  • 7,387

Top 50 recent answers are included