public inbox for [email protected]
help / color / mirror / Atom feedFrom: Dan Langille <[email protected]>
To: Peter Eisentraut <[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 10:23:29 -0400
Message-ID: <3F507B21.17705.2E948175@localhost> (raw)
In-Reply-To: <[email protected]>
References: <3F506503.25957.2E3E1BF3@localhost>
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/
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: <3F507B21.17705.2E948175@localhost>
* 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