Re: MD5 Authentication - Mailing list pgsql-general

From Raimon Fernandez
Subject Re: MD5 Authentication
Date
Msg-id F78EB9CE-14B8-4CE9-AA68-36F444AD2A64@montx.com
Whole thread Raw
In response to Re: MD5 Authentication  (John DeSoi <desoi@pgedit.com>)
Responses Re: MD5 Authentication  (Raimon Fernandez <coder@montx.com>)
List pgsql-general
I'm blocked .......


On 06/11/2009, at 6:27, John DeSoi wrote:

>
> On Nov 5, 2009, at 12:35 PM, Raimon Fernandez wrote:
>
>> at least, my first md5 (psw+user) is the same as the pg_shadow
>> (wihtout the 'md5') ...
>>
>> should I md5 the first md5 as I get it as string (like username) or
>> byte by byte ?
>
> As far as I know, a string. But it is unclear to me what happens
> when the user or database name has non-ascii characters. The client
> encoding is not established until after authentication.
>
> I asked about that a while ago but did not get any responses.

After reading all the emails about it, I'm blocked, maybe someone can
see where the error is and shade some light on it ...

user: postgres (test values)
psw:postgres (test values)

first md5("postgrepostgres") ==> 44965A835F81EC252D83961D2CC9F3E1

salt: A6B76060


second md5("44965A835F81EC252D83961D2CC9F3E1"+"A6B76060") ==>
34F74BEF877202D4399092F97EFE8712


send to server:  header + length +
"md5"+"34F74BEF877202D4399092F97EFE8712" ==> Fatal error, password
Authentication failed for user postgres ...

thanks,

regards,


raimon


pgsql-general by date:

Previous
From: John R Pierce
Date:
Subject: Re: PostgreSQL for 64 Bit Windows Version
Next
From: Ivan Sergio Borgonovo
Date:
Subject: xml import/export tools and performance