From: niall el-assaad <niallel@gmail.com>
To: pgsql-admin@postgresql.org
Subject: Password recommendations for an appliance
Date: Fri, 11 Jul 2008 10:39:43 +0100
Message-ID: <b594cade0807110239m2fd09f6an229b07f22c75ecb1@mail.gmail.com> (raw)
Hi,
I'm developing an appliance that runs postgresql and will be provided to
many people.
I am wondering on the best way of protecting the database user account.
At the moment the account has no password on it, to me this means that the
only people who can connect are the application (PHP running on the box), or
someone logged in as root at the linux command line of the appliance (which
means they have permission to anything anyway).
In this scenario is it worth putting a password on the user account? The
password would need to be stored in a file on the box anyway (so the root
user could get to it quite easily)?
I'm wondering if there are any best practices for this, as I've seen many
appliances that don't bother with a password, and only a few that do use a
password.
Opinions very welcome.
thanks,
niall
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: niallel@gmail.com
Subject: Re: Password recommendations for an appliance
In-Reply-To: <b594cade0807110239m2fd09f6an229b07f22c75ecb1@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