kev...@consistentstate.com (Kevin Kempter) writes:
> I'm looking for thoughts/feedback on the use of UNIX Sockets vs standard CIDR
> style access (i,e, Ident, MD5, etc) to a Postgres Cluster. What are the
> pros/cons, which is more secure and why, etc...
There is no single answer, which is essent
I think you're confusing the here.
PS. That should have been "I think you're confusing concepts here" -
deleted the wrong word!
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Hi Kevin,
Kevin Kempter wrote:
Hi All;
I'm looking for thoughts/feedback on the use of UNIX Sockets vs
standard CIDR style access (i,e, Ident, MD5, etc) to a Postgres
Cluster. What are the pros/cons, which is more secure and why, etc...
I think you're confusing the here. CIDR refers to a me
Hi All;
I'm looking for thoughts/feedback on the use of UNIX Sockets vs standard CIDR
style access (i,e, Ident, MD5, etc) to a Postgres Cluster. What are the
pros/cons, which is more secure and why, etc...
Thanks in advance
On Wed, 4 Apr 2007, Dave Lazar wrote:
Most likely psql is picking up the password from ~/.pgpass when run as
your
user. Pgadmin3 stores passwords in .pgpass, so it's likely been put in
there
by pgadmin. As a test - move .pgpass to .pgpass.old and try to connect
via
psql -U postgres -d myDataBa
On Wed, 4 Apr 2007, Dave Lazar wrote:
I have a quick question about my installation that puzzles me. pgsql
8.2.3on a debian box. Tested it out the database works. pgadmin III
connects fine
too. I used alter table on the template1 database to give postgres user a
password. I changed pg_hba to use
One quick point - you don't need to alter anything in the template1
database to set user's passwords.
In PgAdmin III - use the "Login roles" section to set the passwords -
that way everything will get committed correctly.
Also, have you restarted PostgreSQL since changing pg_hba.conf?
Andy.
D
On Wed, Apr 04, 2007 at 04:25:17PM -0400, Dave Lazar wrote:
> password. I changed pg_hba to use md5 on all connections including local.
did you restart?
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
Hi,
I have a quick question about my installation that puzzles me. pgsql
8.2.3on a debian box. Tested it out the database works. pgadmin III
connects fine
too. I used alter table on the template1 database to give postgres user a
password. I changed pg_hba to use md5 on all connections including l
On Tue, Oct 22, 2002 at 05:05:38PM +0200, Igor Georgiev wrote:
> or my nightmare a cygwin on Win 98 everybody can can access everything
Or =my= nightmare: Anything important on any Windows platform.
-crl
--
Chad R. Larson (CRL22)[EMAIL PROTECTED]
Eldorado Computing, Inc. 602-604
"Igor Georgiev" <[EMAIL PROTECTED]> writes:
> Ok, but my question actually isn't about pg_hba.conf comments, i read enough
> but what will stop root from adding this lines or doing su - postgres ??
As somebody already pointed out, you *must* trust the people with root
access to your machine; ther
> They can just read the raw database files as
well.
wow I'm not sure
how about this
edit pg_hba.conf
# Allow any user on the local system to connect to
any # database under any
username
local
all
trust
su -
On Tue, 22 Oct 2002, Igor Georgiev wrote:
> > > edit *pg_hba.conf *
> > > # Allow any user on the local system to connect to any
> > > # database under any username, but only via an IP connection:
> > > host all 127.0.0.1 255.255.255.255trust
>
>
> edit *pg_hba.conf *>
> # Allow any user on the
local system to connect to any>
> # database under any
username, but only via an IP connection:>
>
host
all
127.0.0.1 255.255.255.255
trust >
> # The same, over
Unix-sock
On Tue, Oct 22, 2002 at 17:05:38 +0200,
Igor Georgiev <[EMAIL PROTECTED]> wrote:
> Is there any way to prevent superuser to acces the database ?
> I mean something like "GRANT / REVOKE CONNECT" MECHANISM
>
> I have no idea how to prevent root from access data in one of this ways :
> root @ l
edit *pg_hba.conf *
# Allow any user on the local system to connect to any
# database under any username, but only via an IP connection:
host all 127.0.0.1 255.255.255.255trust
# The same, over Unix-socket connections:
local
Is there any way to prevent superuser to acces the
database ?
I mean something like "GRANT /
REVOKE CONNECT" MECHANISM
I have no idea how to prevent root from access data
in one of this ways :
root @ linux:~#su
- postgres
postgres @
linux:/usr/local/pgsql/bin$pg_dump
or
e
Okay, here's my question for the week...
I have a server that I want to run with multiple client databases, each
one password protected...but how do I get it so that userA can't connect
to userB's database, or vice versa?
I know I can grant/revoke on the tables, but how do I grant/revoke on the
18 matches
Mail list logo
