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@xxxxxxxxxx> http://momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
