From: | Karl DeBisschop <karl(at)debisschop(dot)net> |
---|---|
To: | Jens Hartwig <jhartwig(at)debis(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: How passwords can be crypted in postgres? |
Date: | 2001-01-02 12:44:17 |
Message-ID: | 3A51CD21.720D6804@debisschop.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Jens Hartwig wrote:
>
> > [...]
> > Isn't this just as bad? If you store the encrypted password, that doesn't
> > help you in the slightest in this case, because if you can breach the list
> > of encrypted passwords, you still know what you need to send as the
> > "password" from the front end to let you into the database.
> > [...]
>
> If you encrypt the input from the frontend as well and compare the
> encrypted strings it will not help you to look into the list of
> encrypted passwords ... or am I wrong?
Slightly wrong -- you need to fetch the salt from the database first.
But even so, if you then transmit this ENCRYPTED password, it can be
sniffed, and the results of that sniff are all that are needed to
access the system.
--
Karl DeBisschop kdebisschop(at)alert(dot)infoplease(dot)com
Learning Network/Information Please http://www.infoplease.com
Netsaint Plugin Developer kdebisschop(at)users(dot)sourceforge(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Tomasz Janyska | 2001-01-02 14:01:57 | Function TOP |
Previous Message | Betsemes | 2001-01-02 11:51:54 | Hierarchical queries in pgsql |