Re: [HACKERS] What goes into the security doc? - Mailing list pgsql-docs

From Peter Eisentraut
Subject Re: [HACKERS] What goes into the security doc?
Date
Msg-id Pine.LNX.4.44.0308301612470.1118-100000@peter.localdomain
Whole thread Raw
In response to Re: [HACKERS] What goes into the security doc?  ("Dan Langille" <dan@langille.org>)
Responses Re: [HACKERS] What goes into the security doc?  ("Dan Langille" <dan@langille.org>)
List pgsql-docs
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.  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).  Perhaps a "howto" format that you can post on
techdocs might be more appropriate for you.

--
Peter Eisentraut   peter_e@gmx.net


pgsql-docs by date:

Previous
From: "Dan Langille"
Date:
Subject: Re: [HACKERS] What goes into the security doc?
Next
From: "Dan Langille"
Date:
Subject: Re: [HACKERS] What goes into the security doc?