pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Dan Langille <dan@langille.org>
To: Bruce Momjian <pgman@candle.pha.pa.us>
To: PostgreSQL-documentation <pgsql-docs@postgresql.org>
Cc: PostgreSQL-documentation <pgsql-docs@postgresql.org>
Subject: Re: [HACKERS] What goes into the security doc?
Date: Sat, 30 Aug 2003 08:49:07 -0400
Message-ID: <3F506503.25957.2E3E1BF3@localhost> (raw)
In-Reply-To: <200308161641.h7GGfvO08515@candle.pha.pa.us>
References: <20030119234411.S76103-100000@m20.unixathome.org>

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.

This is what I have so far:
  http://www.freebsddiary.org/tmp/PostgreSQL-security.txt

cheers

On 16 Aug 2003 at 12:41, Bruce Momjian wrote:

> 
> Now that we are in beta, does someone want to tackle a "security"
> section in the docs?
> 
> 
> ---------------------------------------------------------------------------
> 
> Dan Langille wrote:
> > With reference to my post to the "PostgreSQL Password Cracker" on
> > 2003-01-02, I've promised to write a security document for the project.
> > Here it is, Sunday night, and I can't sleep.  What better way to get there
> > than start this task...
> > 
> > My plan is to write this in very simple HTML.  I will post the draft
> > document on my website and post the URL here from time to time for
> > feedback. Please make suggestions for content.  So far, I will cover these
> > items:
> > 
> > - .pgpass (see
> > http://developer.postgresql.org/docs/postgres/libpq-files.html)
> > - local connections
> > - remote connections (recommending SSL)
> > - pg_hba (only in passing, most of that is at
> > http://www.postgresql.org/idocs/index.php?client-authentication.html)
> > - running the postmaster as a specific user
> > 
> > That doesn't sound like much.  Surely you can think of something else to
> > add.  Should I post this to another list for their views?
> > 
> > OK, that's done it.  I'm ready for sleep now.
> > 
> > 
> > ---------------------------(end of broadcast)---------------------------
> > TIP 5: Have you checked our extensive FAQ?
> > 
> > http://www.postgresql.org/users-lounge/docs/faq.html
> > 
> 
> -- 
>   Bruce Momjian                        |  http://candle.pha.pa.us
>   pgman@candle.pha.pa.us               |  (610) 359-1001
>   +  If your life is a hard drive,     |  13 Roberts Road
>   +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073
> 


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




view thread (20+ messages)  latest in thread

Message-ID: <3F506503.25957.2E3E1BF3@localhost>
Permalink:  ../3F506503.25957.2E3E1BF3@localhost/
Also on:    postgresql.org/message-id/3F506503.25957.2E3E1BF3@localhost

 · 

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: pgsql-docs@postgresql.org
  Cc: dan@langille.org, pgman@candle.pha.pa.us
  Subject: Re: [HACKERS] What goes into the security doc?
  In-Reply-To: <3F506503.25957.2E3E1BF3@localhost>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox