public inbox for [email protected]
help / color / mirror / Atom feedFrom: Peter Eisentraut <[email protected]>
To: Dan Langille <[email protected]>
Cc: Bruce Momjian <[email protected]>
Cc: PostgreSQL-documentation <[email protected]>
Subject: Re: [HACKERS] What goes into the security doc?
Date: Sat, 30 Aug 2003 16:15:39 +0200 (CEST)
Message-ID: <[email protected]> (raw)
In-Reply-To: <3F506503.25957.2E3E1BF3@localhost>
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 [email protected]
view thread (20+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: [HACKERS] What goes into the security doc?
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox