Re: Possible to store invalid SCRAM-SHA-256 Passwords

From: raf(at)raf(dot)org
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Possible to store invalid SCRAM-SHA-256 Passwords
Date: 2019-04-22 21:49:24
Message-ID: 20190422214924.pytigrzlq7mkdyzq@raf.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Stephen Frost wrote:

> I agree we should also handle md5 better. I realize this needs to be
> back-patched and so we have to deal with the existing catalog structure,
> but this really screams out, in my mind anyway, that we shouldn't have
> ever tried to just stash the password-encoding-type into the password
> field and that we should have pulled it out into its own column, so that
> we aren't having to guess about things as important as a password.
>
> Thanks!
>
> Stephen

I don't think there's anything wrong with prefixing a
password hash with an identifier for the password
hashing scheme (and any parameters for that scheme).
This is done all the time in many systems. It just has
to be unambiguoous.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Geoghegan 2019-04-22 22:03:30 Re: amcheck assert failure
Previous Message Jonathan S. Katz 2019-04-22 20:57:40 Re: Possible to store invalid SCRAM-SHA-256 Passwords