Re: Re: Proposal for encrypting pg_shadow passwords

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Re: Proposal for encrypting pg_shadow passwords
Date: 2001-08-15 19:38:58
Message-ID: 200108151938.f7FJcwo16856@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

> > Bruce Momjian writes:
> >
> > > Attached please find:
> > >
> > > the original proposal to encrypt pg_shadow
> > > a diff of the current CVS
> > > two new files (backend/libpq/md5.c and include/libpq/md5.h)
> > > which implement MD5 encryption (from Vince with cleanups)
> >
> > I also see that the md5.c implementation does not use palloc and makes the
> > rather odd assumption that long int == unsigned64.

Also, I didn't use palloc because the same C code is used in the backend
and libpq.

> That is from Vince's code, I think. Can you suggest a fix?
>
> > What's your rush? Is there a deadline now?
>
> I want to do SCM patch, then write presentation for LinuxWorld, and go
> to Linuxworld. Then we are at the end of August. Also, people need to
> do the Java MD5 code, and if I want that before we start 7.2 beta, I
> feel rushed.

It is not knowing how quickly the ODBC/JDBC people can handle this that
has me a little worried.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Gerhard Häring 2001-08-15 20:15:36 Re: Fix for fetchone() and fetchmany() in Python interface
Previous Message Gerhard Häring 2001-08-15 19:25:52 Re: Fix for fetchone() and fetchmany() in Python interface