Hi all,
I am working on an installer for my program that creates a postgres
database and user (the installer is written in perl and runs as 'root').
I want to find a way to let the user set the password on the new
database and have postgres actually ask for it without editing the
default
Madison Kelly [EMAIL PROTECTED] writes:
I want to find a way to let the user set the password on the new
database and have postgres actually ask for it without editing the
default 'pg_hba.conf' file, if at all possible.
There is no such animal as a database password in PG. There are user
Tom Lane wrote:
Madison Kelly [EMAIL PROTECTED] writes:
I want to find a way to let the user set the password on the new
database and have postgres actually ask for it without editing the
default 'pg_hba.conf' file, if at all possible.
There is no such animal as a database password in PG.
On Fri, Dec 16, 2005 at 02:09:52PM -0500, Madison Kelly wrote:
May I ask then? What *is* considered best practices for securing a
database in PostgreSQL? Assuming I leave the 'pg_hba.conf' file at it's
default values, is there any real point to having a password on a
postgresql user
Madison Kelly [EMAIL PROTECTED] writes:
May I ask then? What *is* considered best practices for securing a
database in PostgreSQL? Assuming I leave the 'pg_hba.conf' file at it's
default values, is there any real point to having a password on a
postgresql user account?
Well, if there were
Martijn van Oosterhout wrote:
On Fri, Dec 16, 2005 at 02:09:52PM -0500, Madison Kelly wrote:
May I ask then? What *is* considered best practices for securing a
database in PostgreSQL? Assuming I leave the 'pg_hba.conf' file at it's
default values, is there any real point to having a password
Tom Lane wrote:
Madison Kelly [EMAIL PROTECTED] writes:
May I ask then? What *is* considered best practices for securing a
database in PostgreSQL? Assuming I leave the 'pg_hba.conf' file at it's
default values, is there any real point to having a password on a
postgresql user account?
Madison Kelly [EMAIL PROTECTED] writes:
Oh shoot, I really wasn't very verbose, was I? Sorry about that.
[ default pg_hba.conf with only ident lines ]
Ah, that explains your question about whether passwords were good for
anything at all. With this pg_hba.conf they aren't --- the server will
Tom Lane wrote:
Madison Kelly [EMAIL PROTECTED] writes:
Oh shoot, I really wasn't very verbose, was I? Sorry about that.
[ default pg_hba.conf with only ident lines ]
Ah, that explains your question about whether passwords were good for
anything at all. With this pg_hba.conf they aren't
[EMAIL PROTECTED] (Madison Kelly) writes:
In this case I can't predict what a given install's postgresql
will be used for (outside of my program) because it is meant for
general distribution (it's a backup program). This obviously makes
things a lot more complicated. :p
No, it oughtn't.
10 matches
Mail list logo
