From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Uwe C. Schroeder <uwe@oss4u.com>
Cc: PostgreSQL Admin <pgsql-admin@postgresql.org>
Subject: Re: Installing PostgreSQL as "postgress" versus "root"
Date: Thu, 13 Jan 2005 15:36:16 -0600
Message-ID: <1105652176.24795.106.camel@state.g2switchworks.com> (raw)
In-Reply-To: <200501131313.39366.uwe@oss4u.com>
References: <4001DEAF7DF9BD498B58B45051FBEA650207AB73@25exch1.vicorpower.vicr.com>
<200501131313.39366.uwe@oss4u.com>
On Thu, 2005-01-13 at 15:13, Uwe C. Schroeder wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Thursday 13 January 2005 10:52 am, Goulet, Dick wrote:
> > Doug,
> >
> > OK, Assume that the binaries are installed under root, but a
> > hacker cracks PostGres, what is to stop him/her from trashing all of the
> > database files in the first place? Their not owned by root. Installing
> > malware, whether it's actual code or destroying/defacing files causes
> > similar if not identical problems. At least their restricted to the
> > postgres user. And in my book the executables are of zero value whereas
> > the data files, and their contained data, are of infinite value. So
> > under your scheme we're protecting the least valuable part of the
> > system at the expense of the most valuable.
>
> So where is the difference? If all executables AND the data is under the
> postgres account - an intruder hacking the postgres account would still be
> able to destroy your data.
> BTW: most commercial software needs root access to be installed - and be it
> just to create the user accounts. It doesn't really matter who owns the
> executables - if the account owning the files is hacked you're screwed
> anyways. When it comes to protecting the data which is the most important
> thing after all, replication and backup are your friends. For my larger
> customers I'm running replication to two offsite servers (one east-coast, one
> texas, just to make sure they're fine when the next earthquake hits) and I do
> backups every 8 hours - which are written to a tape and distributed to
> another set of offsite servers using rdist. So whatever happens the max they
> could ever possibly lose is 8 hours, except there is a full blown nuclear
> attack on the whole US - in which case nobody would care about the data
> anyways.
Like someone pointed out, it might be quite possible to install a
trojaned psql executable or some equivalent to harvest passwords, or
even a version that when executed by root on accident (i.e. the sysadmin
forgets he's logged in as root and runs psql) which then installs a root
kit.
Also, it might make it easier for a hacker to cover his tracks if he can
write to the postgresql binaries.
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: smarlowe@g2switchworks.com, uwe@oss4u.com
Subject: Re: Installing PostgreSQL as "postgress" versus "root"
In-Reply-To: <1105652176.24795.106.camel@state.g2switchworks.com>
References: <4001DEAF7DF9BD498B58B45051FBEA650207AB73@25exch1.vicorpower.vicr.com> <200501131313.39366.uwe@oss4u.com> <1105652176.24795.106.camel@state.g2switchworks.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