253
Comments
  • 4
    *cough* heh
  • 42
    "Sorry, that password is already taken by Palethron. Please chose another password."

    However. The hashing *should* make everything unique.
  • 18
    @Tobyvw if salt(s) are random and collision probability is low enough, yes. But when someone asks it like that I wonder if passwords aren't stored in plain text...
    Were they?
  • 1
    Must be a mistake
  • 1
    These are the solutions higher ups come with without consulting anyone.
  • 4
    @Hallelouia their assumption was that the passwords were stored in plaintext and did not want to allow two users to use the same password. i can’t even remember the reason for this request. the reason for the request is not so idiotic as this solution which someone came up with.
  • 2
    Funniest thing I've read all day lololol
  • 3
    Way to collect unique passwords
  • 1
  • 2
    Hahahahaha secure af mate.

    I think I’ve seen posts about this sort of nonsense before on plain text offenders.
  • 1
    when you are using salt would this be no problem, but in pratice.....
    no
  • 1
    Was just rethinking about this, but if you salt correctly and use correct hashing you should actually not have duplicate password hashes in your database, since you are not supposed to have collision. I guess unique could prevent saving collided hashes but I don't know how relevant that would be...
Add Comment