From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | rjb(at)xs4all(dot)nl (Ronald Baljeu) |
Cc: | rjb(at)xs4all(dot)nl, dlorenso(at)afai(dot)com, pgsql-hackers(at)hub(dot)org |
Subject: | Re: [HACKERS] Solution to the pg_user passwd problem !?? (c) |
Date: | 1998-02-20 16:16:17 |
Message-ID: | 199802201616.LAA05045@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>
> > >
> > > > ------- OTHER WISE ---- CAN WE STEAL IDEAS FROM OTHERS? --------
> > > >
> > > > I'm also running MySQL (trying to switch to PG, but waiting for ODBC
> > > > to catch up), I like the mysql feature of inserting passords by:
> > > >
> > > > insert into user (host,user,password)
> > > > values ("domain.com","dlorenso",password('psswrd');
> > >
> > > Hmmm... When I read this, another (related) idea pops into my head.
> > > It's probably nothing, but:
> > >
> > > what about defining a new type 'passwd', with
> > > an input (or output) routine which does the crypting?
> >
> > If they do a binary cursor, does the output function get called?
>
> Oops, I haven't thought about that. I guess it doesn't :(
> Ok, what about an input routine that does the crypting?
>
> One down, one to go...
>
> Cheers,
> Ronald
>
Then, the backend can't find the original password to test the random
salt on.
--
Bruce Momjian
maillist(at)candle(dot)pha(dot)pa(dot)us
From | Date | Subject | |
---|---|---|---|
Next Message | Dwayne Bailey | 1998-02-20 16:18:45 | Re: [HACKERS] Who is everyone? |
Previous Message | D. Jay Newman | 1998-02-20 16:08:37 | Re: [HACKERS] Who is everybody? |