Re: [HACKERS] Connection to PostgreSQL Using Certificate: Wrong Permissions on Private Key File

From: "korry" <korry(dot)douglas(at)enterprisedb(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Kevin Hunter" <hunteke(at)earlham(dot)edu>, "Angus Black Atkins-Trimnell" <trimnell(at)uic(dot)edu>, "Postgres General List" <pgsql-general(at)postgresql(dot)org>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] Connection to PostgreSQL Using Certificate: Wrong Permissions on Private Key File
Date: 2008-03-31 22:55:15
Message-ID: 47F16BD3.8030408@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers


> Now libpq doesn't have any provision for DETAIL or HINT in its
> locally-generated messages at the moment, so we can't just duplicate
> the backend message, but we could do something like this example
> from elsewhere in libpq:
>
> if (stat_buf.st_mode & (S_IRWXG | S_IRWXO))
> {
> fprintf(stderr,
> libpq_gettext("WARNING: password file \"%s\" has world or group read access; permission should be u=rw (0600)\n"),
> pgpassfile);
> return NULL;
> }
>
Hmmm... I'm not crazy about libpq printing error messages to stderr.
The client application can't intercept those messages. And those
messages will often get lost - many client applications don't have
useful stderr streams (think GUI application on Win32).

-- Korry

--

Korry Douglas <korryd(at)enterprisedb(dot)com>
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Michelle Konzack 2008-04-01 00:17:06 FW by pgsql-general-owner@postgresql.org : [pgsql-general] Daily digest v1.8030 (22 messages)
Previous Message Olexandr Melnyk 2008-03-31 20:52:57 Re: GSoC Proposal: PL/Mono

Browse pgsql-hackers by date

  From Date Subject
Next Message Rafael Martinez 2008-03-31 23:02:34 Guessing future postgresql features
Previous Message Magnus Hagander 2008-03-31 20:23:32 Re: POSIX shared memory support