Magnus Hagander wrote:
> I notice our docs have:
>
> If you are at all concerned about password
> sniffing attacks then md5 is preferred, with
> crypt to be used only if you must support pre-7.2
> clients. Plain password should be avoided especially for
>
>
> At what point do we
Peter Eisentraut wrote:
> Tom Lane wrote:
>> Peter Eisentraut <[EMAIL PROTECTED]> writes:
>>> AFAICT, removing an authentication method requires a protocol version
>>> bump.
>>
>> Why would it require that? There would just be some auth method codes
>> that remain reserved but aren't used anymore.
Tom Lane wrote:
Peter Eisentraut <[EMAIL PROTECTED]> writes:
AFAICT, removing an authentication method requires a protocol version
bump.
Why would it require that? There would just be some auth method codes
that remain reserved but aren't used anymore.
Yeah, I was mistaken. AuthenticationC
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> AFAICT, removing an authentication method requires a protocol version
> bump.
Why would it require that? There would just be some auth method codes
that remain reserved but aren't used anymore.
regards, tom lane
--
Sent vi
Magnus Hagander wrote:
I notice our docs have:
If you are at all concerned about password
sniffing attacks then md5 is preferred, with
crypt to be used only if you must support pre-7.2
clients. Plain password should be avoided especially for
At what point do we just remove the