pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <bruce@momjian.us>
To: Magnus Hagander <magnus@hagander.net>
Cc: Shane Ambler <pgsql@007Marketing.com>
Cc: Michael Schmidt <michaelmschmidt@msn.com>
Cc: PostgreSQL General <pgsql-general@postgresql.org>
Subject: Re: Password issue revisited
Date: Tue, 20 Feb 2007 10:21:21 -0500 (EST)
Message-ID: <200702201521.l1KFLL823218@momjian.us> (raw)
In-Reply-To: <20070220150507.GD11927@svr2.hagander.net>

Magnus Hagander wrote:
> Are we sure we want to do this? (Sorry, didn't notice this thread last
> time)
> 
> The default on *all* windows versions since NT 4.0 (which is when the
> directory we use was added) will put this file in a protected directory.
> The only case when it's not protected by default is if you're usnig FAT
> filesystem, in which case there is nothing you can do about it anyway.
> On unix, the file will often be created in outside-readable mode by
> default, depending on how your OS is set up.
> 
> So to reach a situation where the file lives in an unprotected
> directory, you must actively open up the directory in question. Which is
> hidden from default view, so you really need to know what you're doing to
> get there.
> 
> Not to mention it's a pain to define what permissions are ok and what
> are not. We're talking ACLs and not filemodes - so how do you decide
> which accounts are ok to have access, and which are not?

OK, I added a comment to fe-connect.c explaining why we don't need to
check the permissions of .pgpass, and removed the TODO.  Thanks.

-- 
  Bruce Momjian  <bruce@momjian.us>          http://momjian.us
  EnterpriseDB                               http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +



view thread (21+ messages)  latest in thread

Message-ID: <200702201521.l1KFLL823218@momjian.us>
Permalink:  ../200702201521.l1KFLL823218@momjian.us/
Also on:    postgresql.org/message-id/200702201521.l1KFLL823218@momjian.us

 · 

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: bruce@momjian.us, magnus@hagander.net, pgsql@007Marketing.com, michaelmschmidt@msn.com, pgsql-general@postgresql.org
  Subject: Re: Password issue revisited
  In-Reply-To: <200702201521.l1KFLL823218@momjian.us>

* 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