From: "Dan Langille" <dan@langille.org>
To: Peter Eisentraut <peter_e@gmx.net>
Date: Sat, 30 Aug 2003 10:23:29 -0400
MIME-Version: 1.0
Subject: Re: [HACKERS] What goes into the security doc?
Cc: Bruce Momjian <pgman@candle.pha.pa.us>,
	PostgreSQL-documentation <pgsql-docs@postgresql.org>
Message-ID: <3F507B21.17705.2E948175@localhost>
References: <3F506503.25957.2E3E1BF3@localhost>
In-reply-to: <Pine.LNX.4.44.0308301612470.1118-100000@peter.localdomain>
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body

On 30 Aug 2003 at 16:15, Peter Eisentraut wrote:

> Dan Langille writes:
> 
> > I've started.  I'm wondering how much we need to cover here and how
> > much can be delegated to other sections of the documentation.  Before
> > I get very far into this, I want to get some ideas as to what we
> > need.
> 
> If you intend this to go into the main documentation, then I think we
> don't need anything, because everything is already documented in its
> proper place.

It has already been decided that we need something.  Hence the 
request for someone to write it and my start on the task.

> What you wrote is basically just a summary of various
> system aspects that might have to do with that vague word "security",
> together with pointers to the places where they are documented (which
> reinforces my point).

Your point being that we don't need anything more than we already 
have?  That conflicts with what has already been decided.

> Perhaps a "howto" format that you can post on
> techdocs might be more appropriate for you.

I'm not sure what you mean by "for you".


-- 
Dan Langille : http://www.langille.org/