News for hackers. Stuff that matters.
Re:Substack's UI and 1Password temporarily cost me $2k by KMag on Tuesday March 23, 2021 @06:38AM (#26553339)
Nit: I think you mean hashing, not encryption.

Though, my bank uses a dual-password setup where the first password is required in its entirety and a few letters of the second password are required. I suspect this is stored by using a (hopefully memory-hard) salted key derivation function/password hash function (such as Argon2 or scrypt) to derive an encryption key from the first password, which is then used to decrypt the second password.

At least, that's the way I'd design the system to minimize consequences of database compromise. Users are often not creative and often use related passwords. You'd want all of the stored information about the second password to provide clues to the first password only if the attacker had already cracked the first password. Hashing all of the permutations really blows up storage space and DB I/O.

Re:Substack's UI and 1Password temporarily cost me $2k by tinus_hn on Tuesday March 23, 2021 @07:42AM (#26553839)
Hashing in this sense is one way encryption.
Re:Substack's UI and 1Password temporarily cost me $2k by KMag on Thursday March 25, 2021 @11:41PM (#26588532)
Cryptographic literature often mentions one-way functions, but I don't think I've ever seen the phrase "one way encryption" in a cryptographic paper. It's not a phrase used by cryptographers, except rarely to describe encryption using trap door one-way functions such as RSA.