Re: [Dbconfig-common-devel] Re: Best practice for allowing access to a postgres db

To: Martin Pitt <mpitt@debian.org>
Cc: sean finney <seanius@debian.org>, dbconfig-common-devel@lists.alioth.debian.org, debian-webapps@lists.debian.org
Subject: Re: [Dbconfig-common-devel] Re: Best practice for allowing access to a postgres db
From: Karsten Hilbert <Karsten.Hilbert@gmx.net>
Date: Mon, 26 Sep 2005 20:08:33 +0200
Message-id: <[🔎] 20050926180832.GD3407@merkur.hilbert.loc>
In-reply-to: <[🔎] 20050926054645.GD16581@box79162.elkhouse.de>
References: <20050615133149.GE6003@ibook.steinmann.cx> <20050616023608.GC16220@gwolf.org> <20050616060154.GF5880@ibook.steinmann.cx> <20050617072430.GA7784@piware.de> <20050617140752.GB30503@seanius.net> <[🔎] 20050925161637.GA18526@piware.de> <[🔎] 20050925205719.GA31498@seanius.net> <[🔎] 20050926054645.GD16581@box79162.elkhouse.de>

On Mon, Sep 26, 2005 at 07:46:45AM +0200, Martin Pitt wrote:

>   --method: defaults to "md5" for TCP connections, and "ident
>     sameuser" for Unix socket connections
> 
> Please let me know whether you really need more complexity.
The above would be sufficient for GNUmed.

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

Reply to:

References:
- Re: Best practice for allowing access to a postgres db
  - From: Martin Pitt <mpitt@debian.org>
- Re: Best practice for allowing access to a postgres db
  - From: sean finney <seanius@debian.org>
- Re: Best practice for allowing access to a postgres db
  - From: Martin Pitt <mpitt@debian.org>

Prev by Date: Re: [Dbconfig-common-devel] Re: Best practice for allowing access to a postgres db
Next by Date: Re: [Dbconfig-common-devel] Re: Best practice for allowing access to a postgres db
Previous by thread: Re: Best practice for allowing access to a postgres db
Next by thread: webserver config: which solution is recommended ?
Index(es):
- Date
- Thread