Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 650FE9FBD2C for ; Thu, 1 Mar 2007 10:08:23 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-new, port 10024) with ESMTP id 27943-01 for ; Thu, 1 Mar 2007 10:07:52 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168]) by postgresql.org (Postfix) with ESMTP id 713669FB990 for ; Thu, 1 Mar 2007 10:08:19 -0400 (AST) Received: by ug-out-1314.google.com with SMTP id k3so336265ugf for ; Thu, 01 Mar 2007 06:08:18 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=LaeSJhELOYgYiT4AuwNFAanc1p4n7HuPisMzyG6NDdacMogbbm/DBZXgtp4vgNLak9LcK4H0D8t5E1tR3r3IL/SS4Gmwbb2bJLHMPov1WjV8EI1Zb9JLOzi1POdHZUrvSVIos0DxKSJ+a0dQ8BKxYVhed75Uj2Smp6hDNnhRDhU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=EDwc0NW4O4yCP0bvrxMq26kZJF6ZZtolcvCCUGeQ6Fb29Q78DZbhbdT1ybAAFF1/g1KFvbVj3TugYHT5ohpC+DoBh+HjVqWJxAWqxeVHrz05lOHg/I+VYUI4OdcVuxR51MdLZBezovnsS1sLX7A2LVLnlZoESyKbCe85SsroxVE= Received: by 10.67.117.18 with SMTP id u18mr2036305ugm.1172758097970; Thu, 01 Mar 2007 06:08:17 -0800 (PST) Received: by 10.67.94.13 with HTTP; Thu, 1 Mar 2007 06:08:17 -0800 (PST) Message-ID: <55c095e90703010608w55a44b6ifbec7fe8f9fb98dd@mail.gmail.com> Date: Thu, 1 Mar 2007 11:08:17 -0300 From: "Ezequias Rodrigues da Rocha" To: "John DeSoi" Subject: Re: How to store a password encripted in a user defined table Cc: "Eugenio Flores" , "Andrej Ricnik-Bay" , PostgreSQL In-Reply-To: <95880380-1F04-44B5-9353-BAB84955748E@pgedit.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <675205.64473.qm@web55615.mail.re4.yahoo.com> <95880380-1F04-44B5-9353-BAB84955748E@pgedit.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200703/9 X-Sequence-Number: 27647 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 > --=20 =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-= =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D Atenciosamente (Sincerely) Ezequias Rodrigues da Rocha =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-= =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- A pior das democracias ainda =E9 melhor do que a melhor das ditaduras The worst of democracies is still better than the better of dictatorships http://ezequiasrocha.blogspot.com/