From: | postgresbugs <postgresbugs(at)grifent(dot)com> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: PGPASSWORD |
Date: | 2005-02-26 15:06:22 |
Message-ID: | 4220906E.3000307@grifent.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Bruce Momjian wrote:
<blockquote cite="mid200502261421(dot)j1QELdd27029(at)candle(dot)pha(dot)pa(dot)us"
type="cite">
<pre wrap="">postgresbugs wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Oliver Jowett wrote:
</pre>
<blockquote type="cite">
<pre wrap="">postgresbugs wrote:
</pre>
<blockquote type="cite">
<pre wrap="">The functionality provided by PGPASSWORD should not be removed unless
there is a functionality other than .pgpass, which is fine for some
uses and not for others, that will provide similar functionality.
That could be psql and pg_dump and the like accepting a password on
the command line as I stated earlier.
</pre>
</blockquote>
<pre wrap="">
Putting the password on the command line would be even more of a
security problem than PGPASSWORD is now. I agree that an alternative
to ,pgpass would be useful, but it needs to be a *secure* alternative.
-O
</pre>
</blockquote>
<pre wrap="">That may be true. Again, I think the option to use or not use PGPASSWORD
or something similar should be up to the system administrator.
</pre>
</blockquote>
<pre wrap=""><!---->
I have updated the docs to read "not recommended":
authentication. This environment variable is not recommended for security
^^^^^^^^^^^^^^^
n
</pre>
</blockquote>
Thanks.<br>
John Griffiths<br>
</body>
</html>
Attachment | Content-Type | Size |
---|---|---|
unknown_filename | text/html | 1.6 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Jones | 2005-02-26 16:47:37 | Re: BUG #1397: busy-loop hang on web server |
Previous Message | postgresbugs | 2005-02-26 13:56:33 | Re: PGPASSWORD |