From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Pavan Teja <pavan(dot)postgresdba(at)gmail(dot)com> |
Cc: | Mike Porter <mike(at)udel(dot)edu>, Михаил Манерко <asper(at)tagan(dot)ru>, Postgres Bug <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: crypt function crash on postgresql 9.3.20 and 10 |
Date: | 2018-02-02 14:55:10 |
Message-ID: | CAKFQuwZBcDJbe2TTqVq1bu=8fU17S_6gV5vSKmeZ9KwdNP=40A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Fri, Feb 2, 2018 at 7:50 AM, Pavan Teja <pavan(dot)postgresdba(at)gmail(dot)com>
wrote:
>
>
> On Feb 2, 2018 8:15 PM, "Mike Porter" <mike(at)udel(dot)edu> wrote:
>
> On Fri, 2 Feb 2018, Михаил Манерко wrote:
>
> If you send an asterisk in the crypt function, the function crashes.
>>
>>
>> example
>>
>> i=# select crypt('123','*');
>> ОШИБКА: invalid salt
>> i=#
>>
>
> The second argument is the salt, and you have not passed enough bits
> for the default hash type.
>
> i=> select crypt( '123', 'aa' );
> crypt
> ---------------
> aamrgyQfDFSHw
> (1 row)
>
>
> Hi,
> Yeah Mike what u said is correct, the consistency of bits
> for generation of salt depends on algorithms like blow fish, md5 etc
>
You sure? Don't have time to show otherwise but the docs suggest what you
are doing is validating a store encrypted password as opposed to encrypting
the provided one.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Михаил Манерко | 2018-02-02 14:58:34 | Re: crypt function crash on postgresql 9.3.20 and 10 |
Previous Message | David G. Johnston | 2018-02-02 14:51:07 | Re: crypt function crash on postgresql 9.3.20 and 10 |