Re: Bugtraq: Having Fun With PostgreSQL - Mailing list pgsql-hackers

From Andrew Hammond
Subject Re: Bugtraq: Having Fun With PostgreSQL
Date
Msg-id 5a0a9d6f0706261110l7e365cd0o787db86b51ae8dde@mail.gmail.com
Whole thread Raw
In response to Re: Bugtraq: Having Fun With PostgreSQL  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Bugtraq: Having Fun With PostgreSQL  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 6/25/07, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> "Andrew Hammond" <andrew.george.hammond@gmail.com> writes:
> > On 6/25/07, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> >> The normal build process for any open-source package is
> >>
> >> ./configure
> >> make
> >> sudo make install
> >> ... now what?  OK, time to read the manual ...
>
> > Since they presumably don't know about initdb yet, yeah, I figure
> > they'll be reading the manual. We already talk  about how to initdb.
> > It seems reasonable to have the manual talk about how to initially
> > connect to your "secure by default" database and create a
> > non-superuser working user.
>
> +1 on having such a discussion in the manual (someone else suggested
> that already IIRC).  But I'm not seeing what a configure flag brings
> to the party.

Like Andrew Sullivan said above, if we want to achieve the dubious
goal of being "secure by default" this seems like the least invasive
way to change the process so that we can be buzzword compliant.

Andrew


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Arrange for quote_identifier() and pg_dump to not quote keywords
Next
From: Tom Lane
Date:
Subject: Re: Bugtraq: Having Fun With PostgreSQL