Robert Treat wrote:
> I'm not sure how adequately these topics are covered elsewhere, but you
> should probably provide at least a pointer if not improved information:
>
> * Should have a mention of the pgcrypto code in contrib.
>
> * Brain hiccup, but isn't there some type of "password" datatype
Kings-Lynne" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, January 24, 2003 10:00 AM
Subject: Re: [HACKERS] What goes into the security doc?
> On 22 Jan 2003 at 13:29, Christopher Kings-Lynne wrote:
>
> > Recommend always running "initdb -W" and s
On 22 Jan 2003 at 13:29, Christopher Kings-Lynne wrote:
> Recommend always running "initdb -W" and setting all pg_hba entries to md5.
Thanks. I also encountered this item on IRC:
[09:26] Guys, is there a problem with using /bin/true of
/bin/false as the shell of the postgres user? The docs on
AIL PROTECTED]
> Subject: Re: [HACKERS] What goes into the security doc?
>
>
> I'm not sure how adequately these topics are covered elsewhere, but you
> should probably provide at least a pointer if not improved information:
>
> * Should have a mention of the pgcrypto code in con
I'm not sure how adequately these topics are covered elsewhere, but you
should probably provide at least a pointer if not improved information:
* Should have a mention of the pgcrypto code in contrib.
* Brain hiccup, but isn't there some type of "password" datatype
* Explanation of problems/solu
With reference to my post to the "PostgreSQL Password Cracker" on
2003-01-02, I've promised to write a security document for the project.
Here it is, Sunday night, and I can't sleep. What better way to get there
than start this task...
My plan is to write this in very simple HTML. I will post th
