Date: Sun, 31 Aug 2003 11:55:14 +0200 (CEST)
From: Peter Eisentraut <peter_e@gmx.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>, Dan Langille <dan@langille.org>,
	PostgreSQL-documentation <pgsql-docs@postgresql.org>
Subject: Re: [HACKERS] What goes into the security doc? 
In-Reply-To: <2160.1062280259@sss.pgh.pa.us>
Message-ID: <Pine.LNX.4.44.0308311126090.1119-100000@peter.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Tom Lane writes:

> As I think Peter is trying to point out, you could almost get the same
> result just by having a fat index entry under "security", but I think
> people are more likely to notice a chapter or section in the Admin Guide
> with such a title.  Also, once we have such a chapter, we might find it
> reads more naturally to move some of the existing discussions into it,
> leaving only a cross-reference where the material is now.

These are the topics that Dan has identified so far:

file security
database users and privileges
client authentication
libpq password files
external libraries

It makes no sense to put all these topics into one chapter, because they
have nothing in common (except "security"): they apply in different stages
of PostgreSQL use, they are managed by different programs and
environments, and they affect different people.