Re: pgsql-server/src/interfaces/libpq fe-connect.c

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: "Bruce Momjian - CVS" <momjian(at)postgresql(dot)org>, <pgsql-committers(at)postgresql(dot)org>
Subject: Re: pgsql-server/src/interfaces/libpq fe-connect.c
Date: 2002-08-30 02:15:02
Message-ID: GNELIHDDFBOCMGBFGEFOIEPFCDAA.chriskl@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Does this patch also check that it's not world-writable?

Chris

> -----Original Message-----
> From: pgsql-committers-owner(at)postgresql(dot)org
> [mailto:pgsql-committers-owner(at)postgresql(dot)org]On Behalf Of Bruce Momjian
> - CVS
> Sent: Friday, 30 August 2002 7:07 AM
> To: pgsql-committers(at)postgresql(dot)org
> Subject: [COMMITTERS] pgsql-server/src/interfaces/libpq fe-connect.c
>
>
> CVSROOT: /cvsroot
> Module name: pgsql-server
> Changes by: momjian(at)postgresql(dot)org 02/08/29 19:06:32
>
> Modified files:
> src/interfaces/libpq: fe-connect.c
>
> Log message:
> > > > > If you want to put in security restrictions that
> are actually useful,
> > > > > where is the code to verify that PGPASSWORDFILE points at a
> > > > > non-world-readable file? That needs to be there
> now, not later, or
> > > > > we'll have people moaning about backward
> compatibility when we finally
> > > > > do plug that hole.
>
> Alvaro Herrera
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
>

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Alvaro Herrera 2002-08-30 02:26:11 Re: pgsql-server/src/interfaces/libpq fe-connect.c
Previous Message Tom Lane 2002-08-30 02:09:45 Re: pgsql-server/src/include/port hpux.h