> in my applications, i have SSL covering the client->app (browser->PHP code),
> so the sniffing would need to be on the wire from the app-server -> database
> server, which in many cases is the same machine.
>
> my mods don't alter the operation of the server in any respect.
>
> they do, however, allow people the choice of using a traditional
> telnetd/binlogin authentication scheme without resorting to external password
> files.
One good point you have is what do we do with 'password' authentication
once we encrypt pg_shadow. My guess is that we just disallow it. It is
insecure and was only there for clients that couldn't do crypt. They
all have that now. It should just go away. We kept it around for the
secondary password file but those secondary password files are the same
once pg_shadow is encrypted.
One item of my plan is that you can encrypt individual users. You don't
have to do them all at once in case you have older clients for some
users but not others.
-- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610)
853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill,
Pennsylvania19026
