Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search archives
  Advanced Search

Re: [GENERAL] 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: [GENERAL] Connection to PostgreSQL Using Certificate: Wrong Permissions on Private Key File
  • Date: Mon, 31 Mar 2008 18:55:15 -0400
  • Message-id: <47F16BD3.8030408@enterprisedb.com> <text/plain>


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




Home | Main Index | Thread Index

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group