Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 8EA1D9FBDE8 for ; Thu, 1 Mar 2007 11:17:09 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 22520-02 for ; Thu, 1 Mar 2007 11:17:05 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from interscan.indicator.com (mail.indicator.be [193.121.199.3]) by postgresql.org (Postfix) with ESMTP id 426549FBDD5 for ; Thu, 1 Mar 2007 11:17:04 -0400 (AST) Received: from webaccess.indicator.be ([10.100.1.7]) by interscan.indicator.com with InterScan Message Security Suite; Thu, 01 Mar 2007 16:04:37 +0100 Received: from DOMEXT-MTA by webaccess.indicator.bewith Novell_GroupWise; Thu, 01 Mar 2007 16:17:01 +0100 Message-Id: <45E6FC74.A3DD.0030.0@indicator.be> X-Mailer: Novell GroupWise Internet Agent 7.0.1 Date: Thu, 01 Mar 2007 16:16:52 +0100 From: "Bart Degryse" To: "PostgreSQL" Cc: "Ezequias Rodrigues da Rocha" Subject: Re: How to store a password encripted in a userdefinedtable References: <675205.64473.qm@web55615.mail.re4.yahoo.com><55c095e90703010608 w55a44b6ifbec7fe8f9fb98dd@mail.gmail.com><45E6F4ED.A3DD.0030.0@indicator.be ><55c095e90703010658u72d22d38g54256769e01cd8fb@mail.gmail.com><55c095e90703 010702k4920ca20r473154d934c8c8f8@mail.gmail.com> In-Reply-To: <55c095e90703010702k4920ca20r473154d934c8c8f8@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=__Part5175FF74.1__=" X-imss-version: 2.046 X-imss-result: Passed X-imss-approveListMatch: *@indicator.be X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.6 tagged_above=0 required=5 tests=AWL, BAYES_50, FORGED_RCVD_HELO, HTML_40_50, HTML_MESSAGE, UNPARSEABLE_RELAY X-Spam-Level: X-Archive-Number: 200703/13 X-Sequence-Number: 27651 --=__Part5175FF74.1__= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit It doesn't do that for me. I've tried it on three different databases (of two different versions) as three different users and the result is always the same (as it should be): select USER, md5('password') current_user md5 bigdbuser 5f4dcc3b5aa765d61d8327deb882cf99 current_user md5 bigdbsys 5f4dcc3b5aa765d61d8327deb882cf99 current_user md5 logstocksys 5f4dcc3b5aa765d61d8327deb882cf99 Show us some statements. >>> "Ezequias Rodrigues da Rocha" 2007-03-01 16:02 >>> Just another thing. Why md5 function return a different string from user role of postgresql ? It allways put an md5 string concated with another sequence of string. Why does it occurs ? Ezequias 2007/3/1, Ezequias Rodrigues da Rocha : > I know it. Thank you so much. > > Ezequias > Grettings from Brazil. > > 2007/3/1, Bart Degryse : > > > > > > update yourtable set passwordfield = md5(passwordfield) > > > > watch out: md5 is irreversable! you can't "un_md5" > > > > > > >>> "Ezequias Rodrigues da Rocha" 2007-03-01 > > 15:08 >>> > > > > John, > > > > That was what I was looking for for a long time. > > > > Now I will change my teller password account to md5. > > > > Could someone suggest me how to change all passwords (PLAIN) to md5 ? > > > > My real best regards > > Ezequias > > > > 2007/3/1, John DeSoi : > > > MD5 is built-in to PostgreSQL. It is what PostgreSQL itself uses to > > > hash passwords. For example: > > > > > > select md5('this is my password'); > > > > > > md5 > > > ---------------------------------- > > > 210d53992dff432ec1b1a9698af9da16 > > > (1 row) > > > > > > > > > > > > On Mar 1, 2007, at 6:06 AM, Eugenio Flores wrote: > > > > > > > Thanks Andrej. But how can I use such algoritms in postgresql? arey > > > > they defined in a function that I can call? > > > > > > > > Or, do I have to code one of those algorithm to use it in my > > > > application? > > > > > > > > > > > > John DeSoi, Ph.D. > > > http://pgedit.com/ > > > Power Tools for PostgreSQL > > > > > > > > > ---------------------------(end of > > broadcast)--------------------------- > > > TIP 9: In versions below 8.0, the planner will ignore your desire to > > > choose an index scan if your joining column's datatypes do not > > > match > > > > -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Atenciosamente (Sincerely) Ezequias Rodrigues da Rocha =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- A pior das democracias ainda é melhor do que a melhor das ditaduras The worst of democracies is still better than the better of dictatorships http://ezequiasrocha.blogspot.com/ --=__Part5175FF74.1__= Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Description: HTML
It doesn't do that for me. I've tried it on three different databases (of two different versions) as three different users and the result is always the same (as it should be):
 
select USER, md5('password')
 
current_user    md5
bigdbuser       5f4dcc3b5aa765d61d8327deb882cf99
 
current_user    md5
bigdbsys        5f4dcc3b5aa765d61d8327deb882cf99
 
current_user    md5
logstocksys     5f4dcc3b5aa765d61d8327deb882cf99
 
Show us some statements.
 
>>> "Ezequias Rodrigues da Rocha" <ezequias.rocha@gmail.com> 2007-03-01 16:02 >>>
Just another thing.

Why md5 function return a different string from user role of postgresql ?

It allways put an md5 string concated with another sequence of string.

Why does it occurs ?
Ezequias

2007/3/1, Ezequias Rodrigues da Rocha <ezequias.rocha@gmail.com>:
> I know it. Thank you so much.
>
> Ezequias
> Grettings from Brazil.
>
> 2007/3/1, Bart Degryse <Bart.Degryse@indicator.be>:
> >
> >
> > update yourtable set passwordfield = md5(passwordfield)
> >
> > watch out: md5 is irreversable! you can't "un_md5"
> >
> >
> > >>> "Ezequias Rodrigues da Rocha" <ezequias.rocha@gmail.com> 2007-03-01
> > 15:08 >>>
> >
> > John,
> >
> > That was what I was lo oking for for a long time.
> >
> > Now I will change my teller password account to md5.
> >
> > Could someone suggest me how to change all passwords (PLAIN) to md5 ?
> >
> > My real best regards
> > Ezequias
> >
> > 2007/3/1, John DeSoi <desoi@pgedit.com>:
> > > MD5 is built-in to PostgreSQL. It is what PostgreSQL itself uses to
> > > hash passwords. For example:
> > >
> > > select md5('this is my password');
> > >
> > >                 md5
> > > ----------------------------------
> > > 210d53992dff432ec1b1a9698af9da16
> > > (1 row)
> > >
> > >
> > >
> > > On Mar 1, 2007, at 6:06 AM, Eugenio Flores wrote:
> > >
> > > > Thanks Andre j. But how can I use such algoritms in postgresql? arey
> > > > they defined in a function that I can call?
> > > >
> > > > Or, do I have to code one of those algorithm to use it in my
> > > > application?
> > >
> > >
> > >
> > > John DeSoi, Ph.D.
> > > http://pgedit.com/
> > > Power Tools for PostgreSQL
> > >
> > >
> > > ---------------------------(end of
> > broadcast)---------------------------
> > > TIP 9: In versions below 8.0, the planner will ignore your desire to
> > >        choose an index scan if your joining column's datatypes do not
> > >        match
> > >
>


--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- =-=-=-=
                                  Atenciosamente (Sincerely)
                        Ezequias Rodrigues da Rocha
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
A pior das democracias ainda é melhor do que a melhor das ditaduras
The worst of democracies is still better than the better of dictatorships
http://ezequiasrocha.blogspot.com/
--=__Part5175FF74.1__=--