Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 7A2939FB80C for ; Tue, 20 Feb 2007 14:57:18 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-new, port 10024) with ESMTP id 33434-08 for ; Tue, 20 Feb 2007 14:57:14 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from securetrans.mitrust.com (securetrans.mitrust.com [207.250.112.34]) by postgresql.org (Postfix) with ESMTP id 930D59FB7EC for ; Tue, 20 Feb 2007 14:57:15 -0400 (AST) Received: from [10.201.170.131] (tr2925.mi.micorp.com [10.201.170.131]) by securetrans.mitrust.com (Postfix) with ESMTP id 292F87D8075; Tue, 20 Feb 2007 12:57:14 -0600 (CST) Message-ID: <45DB448A.3040308@amsoftwaredesign.com> Date: Tue, 20 Feb 2007 12:57:14 -0600 From: Tony Caduto User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Magnus Hagander , pgsql-general@postgresql.org Subject: Re: Password issue revisited References: <45BCACDB.5050702@007Marketing.com> <200702201449.l1KEn0r21849@momjian.us> <20070220150507.GD11927@svr2.hagander.net> In-Reply-To: <20070220150507.GD11927@svr2.hagander.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=BAYES_50 X-Spam-Level: X-Archive-Number: 200702/1071 X-Sequence-Number: 109561 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. > Is there truly such a thing on a windows PC? All it takes is one Virus or Malware to gain access to the PC and anything stored in the user profile is easy picking. The virus and malware creators may not know about the pg_pass file now, but they will eventually. What about having a wallet type system where the user can create a pass phrase to protect a generated key that would get loaded once per session. That is how KDE allows users to store passwords. I work at a large financial institution and if the auditors knew about the pg_pass being plain text, they would pretty much ban it's use. Anytime a password is sitting on a non encrypted file system, regardless of it's permissions it is potentially at risk. -- Tony