* Antoine Martin (antoine@nagafix.co.uk) wrote:
> Basically, multiple input data that have the same output hash, which is
> of no use when what you are trying to find is the input.
> Finding collisions quicker for a known input is one thing, but that is
> not going to reduce the search space, not even your storage space (it is
> unlikely that the colliding results would all be valid input).
Erm, you aren't necessairly trying to find the input... It may be the
case that you're trying to find what you need to authenticate to this
server, or any other PostgreSQL server where the same userid & input are
used. In that case you just need something that hashes to the same
thing. Using a random salt would mean that it's different per server so
breaking it on one doesn't help you against another server unless you
happened to find the actual original input.
> Is adding the non-guessable salt that hard anyway?
It is if you want to continue to support the 'md5' method in pg_hba.conf
because the wireline protocol will probably need to change. A less
intrusive alternative would be to add an 'with encrypted password 'xyz'
with random salt' or some such which would only be supported with the
'password' method in pg_hba.conf.
One problem with this is that you then can't just switch from password
to md5 or back again. Perhaps that's ok though? Comments?
Stephen
