From: Scott Marlowe <scott.marlowe@gmail.com>
To: Thomas Jacob <jacob@internet24.de>
Cc: Robert Treat <xzilla@users.sourceforge.net>
Cc: pgsql-admin@postgresql.org
Subject: Re: Best practice running a shared DB hosting server
Date: Mon, 18 Aug 2008 10:55:27 -0600
Message-ID: <dcc563d10808180955r7a10dbc1h6b04689f5dad9cf6@mail.gmail.com> (raw)
In-Reply-To: <1219077495.18884.38.camel@enterprise.ims-firmen.de>
References: <1218635097.28547.28.camel@enterprise.ims-firmen.de>
<dcc563d10808130757o45cdeb45jaa87cc09d0bdd837@mail.gmail.com>
<1218642490.28547.50.camel@enterprise.ims-firmen.de>
<200808181148.14557.xzilla@users.sourceforge.net>
<1219077495.18884.38.camel@enterprise.ims-firmen.de>
On Mon, Aug 18, 2008 at 10:38 AM, Thomas Jacob <jacob@internet24.de> wrote:
> On Mon, 2008-08-18 at 11:48 -0400, Robert Treat wrote:
>
>> Yes, I think the whole "security through obscurity" argument is a cop out to
>> get around postgresql's design choices (in this perticular instance anyway,
>> in many cases its valid).
No, it's a way of preventing the wasting of countless man hours making
changes that accomplish exactly nothing in terms of SECURITY. Now, it
may help with your particular business rules to have that information
hidden. But if you think hiding who the other users are gives you any
real measure of security you are sorely mistaken.
> Well, improvements that make PostgreSQL better suited to separating
> databases for different users would surely help drive up
> the number of users. There are lots people who can't
> or don't want to afford their own database server while
> still needing to have access to an SQL database.
I agree that such changes might make it easier for some shops to adopt
postgresql, but I'm not sure it's a win in a cost / benefits analysis.
Very few users actually need to hide user info in the system catalogs
etc from other users. For the vast majority who want it it's not
something they need, just something they'd like. I would much rather
have the hackers working on code to make postgresql more performent
and expanding functionality than hiding information.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: scott.marlowe@gmail.com, jacob@internet24.de, xzilla@users.sourceforge.net
Subject: Re: Best practice running a shared DB hosting server
In-Reply-To: <dcc563d10808180955r7a10dbc1h6b04689f5dad9cf6@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox