From: | Aaron Sethman <androsyn(at)ratbox(dot)org> |
---|---|
To: | "Roderick A(dot) Anderson" <raanders(at)altoplanos(dot)net> |
Cc: | "Silesky Marketing Inc, Support" <support(at)silesky(dot)com>, pgsql <pgsql-sql(at)postgresql(dot)org>, pggeneral <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: password encryption |
Date: | 2000-07-24 22:37:47 |
Message-ID: | Pine.LNX.4.21.0007241835530.25447-100000@squeaker.ratbox.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-sql |
I think what he was looking for was more along the lines of a generic sql
function that hashes a string, and not to update the system tables.
I actually wrote a replacement for the mysql PASSWORD() function that is
actually compatible with the hashing that mysql uses. If you would like a
copy of this function just let me know so I can extract it out of the a
bunch of other functions.
Aaron
On Fri, 21 Jul 2000, Roderick A. Anderson wrote:
> On Fri, 21 Jul 2000, Silesky Marketing Inc, Support wrote:
>
> > Hello,
> >
> > I want to encrypt passwords with Postgresql the way mySQL does it with :
> >
> > UPDATE user SET Password=PASSWORD('new_password') WHERE user='root';
>
> Check out the ALTER command.
>
> ALTER USER username
> [ WITH PASSWORD 'password' ]
> [ CREATEDB | NOCREATEDB ] [ CREATEUSER | NOCREATEUSER ]
> [ VALID UNTIL 'abstime' ]
>
>
> Rod
> --
> Roderick A. Anderson
> raanders(at)altoplanos(dot)net Altoplanos Information Systems, Inc.
> Voice: 208.765.6149 212 S. 11th Street, Suite 5
> FAX: 208.664.5299 Coeur d'Alene, ID 83814
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Paul Caskey | 2000-07-24 22:37:51 | 4 billion record limit? |
Previous Message | Jens P. Elsner | 2000-07-24 22:33:41 | Re: Migrating from Sybase |
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 2000-07-24 22:47:18 | Re: TCL updates |
Previous Message | Jesus Aneiros | 2000-07-24 22:25:03 | RULES on PostgreSQL |