Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id D56E39FB4EC for ; Thu, 1 Mar 2007 10:58:11 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 75289-02 for ; Thu, 1 Mar 2007 10:58:04 -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.171]) by postgresql.org (Postfix) with ESMTP id CA25F9FBAE7 for ; Thu, 1 Mar 2007 10:58:04 -0400 (AST) Received: by ug-out-1314.google.com with SMTP id k3so347123ugf for ; Thu, 01 Mar 2007 06:58:03 -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=UJ7QFuMX3EcnwxS84cn7mO6sQKZLy2jWBhjlMk+0YMWpC0AkdsCYUgXfn7pyU+u0gZNfdEG4SxLmNLwn7qYNI2q2w+wCyCnD33u+bPsqiDf0c0cCsRCwIFQZb1vO6T9MUWxLucnEsmX6UAaVVZHFkv9cnk5p8UDTTAq6M6OAdmo= 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=idGjTIGOpe9QPskmrW6WkXlni653Q/K5l0jzWKCnnzbuU133038BzBRGYMnu560LOWcyv+uuIF0G1be4LZ8RmBchL/MgOcDhDHIeyy+0nSNGqH8LO5xgCMaL47myYpjjGoEKyxHUYpTT7nP1smMBZ5QmmGKEVM83ZVdFkGXFdwU= Received: by 10.67.117.18 with SMTP id u18mr2086356ugm.1172761083273; Thu, 01 Mar 2007 06:58:03 -0800 (PST) Received: by 10.67.94.13 with HTTP; Thu, 1 Mar 2007 06:58:03 -0800 (PST) Message-ID: <55c095e90703010658u72d22d38g54256769e01cd8fb@mail.gmail.com> Date: Thu, 1 Mar 2007 11:58:03 -0300 From: "Ezequias Rodrigues da Rocha" To: "Bart Degryse" Subject: Re: How to store a password encripted in a user definedtable Cc: PostgreSQL In-Reply-To: <45E6F4ED.A3DD.0030.0@indicator.be> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <675205.64473.qm@web55615.mail.re4.yahoo.com> <55c095e90703010608w55a44b6ifbec7fe8f9fb98dd@mail.gmail.com> <45E6F4ED.A3DD.0030.0@indicator.be> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200703/11 X-Sequence-Number: 27649 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 > >