News for hackers. Stuff that matters.
Re:Pgsodium: Modern cryptography for PostgreSQL using libsodium by paulryanrogers on Friday June 12, 2020 @09:50PM (#23505990)
Passwords usually get hashed in app layer so DB never has the key. In the same way encryption is usually done entirely outside DBs as they tend to leak or get breached. So the ciphertext without any potential access to keys is generally acceptable for storing in a DB, ideally isolated for one purpose.
Re:Pgsodium: Modern cryptography for PostgreSQL using libsodium by systemvoltage on Friday June 12, 2020 @10:41PM (#23506267)
This is the correct answer. Hashing can happen at many different layers in the app or even as a ephemeral Postgres function call in the database. Storing hashes is not storing secrets. If one has to worry about exposing the lock to public, then there is something wrong with the security of that lock. Use a better lock.