Julio Leyva wrote:
also make sure you started postgesql with -i option, so you can connect
from the lan
He said he had set listen_addresses to '*', which is equivalent.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of
Now, I have set up all the appropriate port forwarding, made sure that
there
are no problems with firewalls on the server.
Just to make sure there really is no issue with firewall did you try
something like telnet on postgres host and port , like telnet
buggy.pg.net5432, you should get
Peter Eisentraut a écrit :
Julio Leyva wrote:
also make sure you started postgesql with -i option, so you can connect
from the lan
He said he had set listen_addresses to '*', which is equivalent.
to allow every one :
hostall all 0.0.0.0 0.0.0.0
Hi Klay,
On Sat, Dec 15, 2007 at 11:11:53AM +0200, Klay Martens wrote:
I was not quite sure if this is the right forum for this question (if it
aint.oh well).
I have had a postgresql server up and running smoothly for 1.5 years now -
no problems at all..but:
I now need to be able to
In article [EMAIL PROTECTED],
Klay Martens [EMAIL PROTECTED] writes:
I have had a postgresql server up and running smoothly for 1.5 years now -
no problems at all..but:
I now need to be able to administer the server remotely, as well as allow
remote logins from a WAN.
Did you set the
Hi..yes, I have set the listen_addresses to *...rather an obvious first
stop...As I said - I have no problems connecting locally, or on a LAN - no
sweat at all. Simply cannot get the connection to work from another network
over a WAN. I believe the problem stems from my not setting pg_hba.conf
On Sat, Dec 15, 2007 at 01:39:44PM +0200, Klay Martens wrote:
Hi..yes, I have set the listen_addresses to *...rather an obvious first
stop...As I said - I have no problems connecting locally, or on a LAN - no
sweat at all. Simply cannot get the connection to work from another network
over a
also make sure you started postgesql with -i option, so you can connect from
the lan
Julioc.
From: [EMAIL PROTECTED]
To: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] pg_hba.conf is driving me nuts
Date: Sat, 15 Dec 2007 13:39:44 +0200
Hi..yes
; pgsql-admin@postgresql.org
Subject: RE: [ADMIN] pg_hba.conf issue
From: Jayakumar_Mukundaraju [EMAIL PROTECTED]
To: pgsql-admin@postgresql.org
Subject: [ADMIN] pg_hba.conf issue
Date: Mon, 2 Jul 2007 19:21:36 +0530
Hi friends,
I am Jayakumar and new to PostgreSQL world. I am using PostgreSQL
From: Ritu Khetan [EMAIL PROTECTED]
To: Tom Lane [EMAIL PROTECTED]
CC: pgsql-admin@postgresql.org,[EMAIL PROTECTED]
Subject: Re: [ADMIN] pg_hba.conf issue
Date: Tue, 3 Jul 2007 11:01:10 +0530
What does ::1/128 signify?
Its the IPv6 notification to loopback address. In other words
, July 03, 2007 12:25 PM
To: Jayakumar_Mukundaraju
Subject: Re: [ADMIN] pg_hba.conf issue
Can you send me your pg_hba.conf file?
From: Jayakumar_Mukundaraju [EMAIL PROTECTED]
To: Vishal Arora [EMAIL PROTECTED],
pgsql-admin@postgresql.org
Subject: Re: [ADMIN] pg_hba.conf issue
Date: Tue, 3 Jul 2007 10
Arora [EMAIL PROTECTED],
pgsql-admin@postgresql.org
Subject: Re: [ADMIN] pg_hba.conf issue
Date: Tue, 3 Jul 2007 12:38:38 +0530
Hi friends,
I herewith paste my pg_hba.conf file for your reference. This is in
172.16.84.76 system(Server box)
TypeDatabase User IP-Address Method
host
To: Jayakumar_Mukundaraju
Subject: Re: [ADMIN] pg_hba.conf issue
One more thing I forgot to ask do you have root as the database user in your
server?
- Vishal
From: Jayakumar_Mukundaraju [EMAIL PROTECTED]
To: Vishal Arora [EMAIL PROTECTED],
pgsql-admin@postgresql.org
Subject: Re: [ADMIN
Dear Vishal,
Its working fine...Thanks lot...
Thanks Regards
Jayakumar M
-Original Message-
From: Vishal Arora [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 03, 2007 2:12 PM
To: Jayakumar_Mukundaraju
Subject: Re: [ADMIN] pg_hba.conf issue
Is it working now?
From
Ritu Khetan [EMAIL PROTECTED] writes:
# IPv4 local connections:
hostall all 127.0.0.1/32 trust
# IPv6 local connections:
#hostall all ::1/128 trust
#hostall all 172.21.42.121/24 trust
hostall
From: Ritu Khetan [EMAIL PROTECTED]
To: pgsql-admin@postgresql.org
Subject: [ADMIN] pg_hba.conf issue
Date: Mon, 2 Jul 2007 18:40:22 +0530
Hi friends,
We have a product with Postgres 8.1 integrated for installations on
Windows. The standard pg_hba.conf configuration going in the package is
From: Jayakumar_Mukundaraju [EMAIL PROTECTED]
To: pgsql-admin@postgresql.org
Subject: [ADMIN] pg_hba.conf issue
Date: Mon, 2 Jul 2007 19:21:36 +0530
Hi friends,
I am Jayakumar and new to PostgreSQL world. I am using PostgreSQL 8.1.3
in Windows 2000 machine.
My problem is, I am unable to
pgsql-admin@postgresql.org
02/07/2007 09:08 PM Subject
Re: [ADMIN] pg_hba.conf issue
:* Tuesday, 6 March 2007 10:58
*To:* Phillip Smith
*Cc:* pgsql-admin@postgresql.org
*Subject:* Re: [ADMIN] pg_hba.conf putty
hello phillip,
yes, the connection i defined in pgadmin uses localhost:5432.
Still, no success :(
2007/3/6, Phillip Smith [EMAIL PROTECTED]:
What address are you
What address are you connecting to on your desktop computer? You should be
using localhost:5432 which putty will redirect to the server via the SSH
tunnel and the server will connect to PostgreSQL on your behalf.
~p
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL
hello phillip,
yes, the connection i defined in pgadmin uses localhost:5432.
Still, no success :(
2007/3/6, Phillip Smith [EMAIL PROTECTED]:
What address are you connecting to on your desktop computer? You should
be using localhost:5432 which putty will redirect to the server via the
What address are you using for server.ip.address?
I believe this is the address you should put in your pg_hba.conf, not
127.0.0.1.
Then in PgAdmin, connect to localhost:5432.
You can always check your PostgreSQL logs and see what source address
the request is coming from.
Andy.
Moritz
127.0.0.1 to match your
pg_hba.conf
Cheers,
~p
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Moritz Bayer
Sent: Tuesday, 6 March 2007 10:58
To: Phillip Smith
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] pg_hba.conf putty
hello phillip
Yes! that's it, thanks heaps.
I had a .pgpass file in the home directory of the client PC. It's
possible PgAdmin III or some other program created it.
Thanks heaps, now I know it was not actually a security issue with my
server.
On Wed, 2007-02-28 at 17:15 -0800, Jeff Frost wrote:
On Thu, 1
On Thu, 1 Mar 2007, Rob van der Linde wrote:
On that server I have a user account, called ynui, and I also have a
postgres user called ynui, they have the same password. Now the
server's IP is 192.168.0.1
My main postgres conf has in it:
listen_addresses = 'localhost,192.168.0.1'
my
Yes, pgadmin3 uses .pgpass to store its connection info - so that's your
likely culprit.
On Thu, 1 Mar 2007, Rob van der Linde wrote:
I had a .pgpass file in the home directory of the client PC. It's
possible PgAdmin III or some other program created it.
--
Jeff Frost, Owner [EMAIL
Gémes Géza wrote:
I have successfully deployed krb5 or pam (with pam_krb5)
authentication with my clients.
My question is: Can I use both in a failover fashion?
Not in PostgreSQL, but you could probably hook Kerberos into PAM.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
On Tue, 26 Sep 2006, Jeanna Geier wrote:
Hi All-
If I change the hostssl line to: hostssl all all 127.0.0.1/32 md5, restart
the server, and attempt to connect via pgadmin, I see the message 'Connecting
to the database... Failed.' If I attempt to connect to a database using the
command
On Tue, 26 Sep 2006, Jeanna Geier wrote:
Yes, I have ssl=true in postgresql.conf. (password encryption is commented
out - is that OK?: #password_encryption = true)
Also, yes, server.crt is in the 'data' directory of my postgres server, as is
server.key.
And, yes, when I am able to start
On Tue, 26 Sep 2006, Jeff Frost wrote:
It seems that for some reason either your server or your client are not
trying to use SSL. Note the: SSL off in the error message you received.
Do you have a server.crt in the data directory of the postgres server?
I guess I should have also asked if
Frost [EMAIL PROTECTED]
To: Jeanna Geier [EMAIL PROTECTED]
Cc: pgsql-admin@postgresql.org
Sent: Tuesday, September 26, 2006 10:05 AM
Subject: Re: [ADMIN] pg_hba.conf: 'trust' vs. 'md5' Issues
On Tue, 26 Sep 2006, Jeff Frost wrote:
It seems that for some reason either your server or your client
Jeanna Geier [EMAIL PROTECTED] writes:
[ hostssl works with 'trust' but not 'md5' ]
It's only when I change the connection method to 'md5' that I'm running into
problems -- then I cannot connect from pgadmin or the command line.
I experimented with this using CVS HEAD, and found that SSL+md5
On Tue, 26 Sep 2006, Tom Lane wrote:
Jeanna Geier [EMAIL PROTECTED] writes:
[ hostssl works with 'trust' but not 'md5' ]
It's only when I change the connection method to 'md5' that I'm running into
problems -- then I cannot connect from pgadmin or the command line.
As for Jeanna's problem,
On Tue, 26 Sep 2006, Jeff Frost wrote:
As for Jeanna's problem, I don't see any password prompt at all in her
example. I've forgotten the details, but wasn't there a password
prompting problem with 8.0.x on Windows?
It worked great with 8.1.4. Let me download 8.0.8 and try that on Windows
Jeff Frost [EMAIL PROTECTED] writes:
Do you remember if the problem was on the 8.0.8 server side that caused the
lack of prompting?
No, I'm pretty sure it was a client-side issue (and I thought we'd fixed
it by 8.0.8 anyway, so I'm glad to see your test agrees).
Jeanna, do you maybe have a
On Tue, 26 Sep 2006, Tom Lane wrote:
Jeff Frost [EMAIL PROTECTED] writes:
Do you remember if the problem was on the 8.0.8 server side that caused the
lack of prompting?
No, I'm pretty sure it was a client-side issue (and I thought we'd fixed
it by 8.0.8 anyway, so I'm glad to see your test
Jeff Frost [EMAIL PROTECTED] writes:
Interestingly, I receive the same error when I disable SSL on the server:
If SSL is disabled then hostssl lines in pg_hba.conf effectively become
no-ops --- they can never be matched since no incoming connection will
be SSL-ified. So that part of it sounds
On Tue, 26 Sep 2006, Tom Lane wrote:
Jeff Frost [EMAIL PROTECTED] writes:
Interestingly, I receive the same error when I disable SSL on the server:
If SSL is disabled then hostssl lines in pg_hba.conf effectively become
no-ops --- they can never be matched since no incoming connection will
On Tue, 26 Sep 2006, Jeff Frost wrote:
But, when I put the trust line back with hostssl, I do not get connected as
per her original indication. Of course this is with my 8.1.4 windows server
and not 8.0.8. Is it possible that 8.0.8 was more liberal with the hostssl
vs host interpretation if
- Original Message -
From: Jeff Frost [EMAIL PROTECTED]
To: Tom Lane [EMAIL PROTECTED]
Cc: Jeanna Geier [EMAIL PROTECTED]; pgsql-admin@postgresql.org;
pgsql-hackers@postgresql.org
Sent: Tuesday, September 26, 2006 11:40 AM
Subject: Re: [ADMIN] pg_hba.conf: 'trust' vs. 'md5' Issues
On Tue, 26 Sep 2006, Jeanna Geier wrote:
Any thoughts?? Like I said previously, I did build this on Windows from
source so we could use the SSL option.could I have missed something when
I was doing that? (It was my first time and I was following instructions from
the INSTALL docs)
, September 26, 2006 12:16 PM
Subject: Re: [ADMIN] pg_hba.conf: 'trust' vs. 'md5' Issues
On Tue, 26 Sep 2006, Jeanna Geier wrote:
Any thoughts?? Like I said previously, I did build this on Windows from
source so we could use the SSL option.could I have missed something
when I was doing
Jeanna Geier wrote:
Searched again for 'pgpass' and for the 'Application Data' directory with
no luck...
The file is called pgpass.conf on Windows. As for the Application
Data, it may be called differently if your Windows is localized -- try
looking for %APPDATA%. (I think I'd do this by
On Tue, 26 Sep 2006, Alvaro Herrera wrote:
Jeanna Geier wrote:
Searched again for 'pgpass' and for the 'Application Data' directory with
no luck...
The file is called pgpass.conf on Windows. As for the Application
Data, it may be called differently if your Windows is localized -- try
]; Tom Lane [EMAIL PROTECTED];
pgsql-admin@postgresql.org; pgsql-hackers@postgresql.org
Sent: Tuesday, September 26, 2006 12:35 PM
Subject: Re: [ADMIN] pg_hba.conf: 'trust' vs. 'md5' Issues
On Tue, 26 Sep 2006, Alvaro Herrera wrote:
Jeanna Geier wrote:
Searched again for 'pgpass
To: Adam Fernie; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] pg_hba.conf includes
hostdbname all @myhosts 255.255.255.255 md5
If I put a single ip or hostname in the file it works a treat but I
don't know how to include more than 1 host or IP address is the file.
Should
hostdbname all @myhosts 255.255.255.255 md5
If I put a single ip or hostname in the file it works a treat but I
don't know how to include more than 1 host or IP address is the file.
Should it be comma seperated, newline for each file or something
different?
You can add
Does your pg_ident.conf contain anything with reference to testusr? As it
seems to be trying Ident authentication over everything else and failing.
Andy
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of ow
Sent: Monday, 06 March, 2006 1:02 PM
To:
In postgresql.conf I have #listen_addresses = 'localhost' and I am logged in
directly into the box, without telnet, ssh or whatever.
But psql -U postgres -h localhost DID WORK (after I entered the password) and
that's a big step forward, thanks.
I'm still not sure why I needed to enter the
On Mon, 6 Mar 2006, ow wrote:
PostgreSQL 8.1.0 on i486-pc-linux-gnu, compiled by GCC cc (GCC) 4.0.3 2005
(prerelease) (Debian 4.0.2-4)
Hi,
Can't get pg_hba.conf with trust to work:
[EMAIL PROTECTED]:~$ psql -U postgres
psql: FATAL: Ident authentication failed for user postgres
To: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] pg_hba.conf + all + trust = Ident authentication failed
for user postgres
In postgresql.conf I have #listen_addresses = 'localhost' and I am logged
in
directly into the box, without telnet, ssh or whatever.
But psql -U postgres -h localhost DID WORK
Have you also changed your pg_ident.conf to map the user gowri to a
database user, and does that database user exist in pgSQL?
By default 127.0.0.1 is set up as trust authentication, so if you
haven't changed this, it will always let you through no matter what
username/password you give.
Andy
On Thu, 29 Sep 2005, Ben Sullins wrote:
I logged onto the linux box via ssh and edited the file by adding a line
in pg_hba.conf for my ip. I'm thinking it other lines above my new entry
could be affecting my access restrictions. Below are the lines in order
as they appear in pg_hba.conf. Any
According to the excelent doc, the _first_ matching entry will be used.
C:\ -Original Message-
C:\ From: Dick Davies [mailto:[EMAIL PROTECTED]
C:\ Sent: Dienstag, 22. Februar 2005 12:57
C:\ To: PostgreSQL Admin
C:\ Subject: [ADMIN] pg_hba.conf
C:\
C:\
C:\
C:\ Just needed clarification
* K?PFERL Robert [EMAIL PROTECTED] [0228 12:28]:
According to the excelent doc, the _first_ matching entry will be used.
If that were true, the below would work, surely?
C:\ I have this:
C:\
C:\ [EMAIL PROTECTED]:postgresql80-server$ cat /opt/pgsql/data/pg_hba.conf
C:\ # TYPE DATABASE
* Donald Fraser [EMAIL PROTECTED] [0257 13:57]:
If postgres has ssl enabled then it will by default negotiate to use ssl,
regardless of the host or hostssl settings in pg_hba. Your client software
needs to refuse ssl connections then it will fall back to a non-ssl
connection so long as there
On Tue, Feb 22, 2005 at 11:56:41 +,
Dick Davies [EMAIL PROTECTED] wrote:
Just needed clarification on how pg_hba.conf operates.
Does a specific host take precedence over a more general network setting?
No. The first line that matches the triple connection type, database name
and user
Bruno Wolff III [EMAIL PROTECTED] writes:
The host entry is the one that applies. But the host entry will allow either
ssl or nonssl, so it doesn't do what you want without cooperation from the
connecting client. You can use hostnossl to match without allowing ssl.
You will also want to use a
* Tom Lane [EMAIL PROTECTED] [0218 15:18]:
Perhaps easier would be to set PGSSLMODE=allow (or even disable) in
the client environment. This will work for libpq-based clients; there
may be something equivalent if you are using other software.
Thanks Tom, I'll give that a go.
Also: why
, 2004 10:12 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [ADMIN] pg_hba.conf
Hi Jim,
I apologize, but it seems that this is the first time that I received an
email from you, but I did receive some emails from others about this
issue, which I had been responding to. Or maybe, I'm not subscribed
[EMAIL PROTECTED] wrote:
Jim said:
Try changing the 10.29.15.0255.255.255.0 to 10.29.15.0/24, if
you
have a 7.4-series pgsql server, and see if that doesn't work.
IT WORKED! Thanks so much Jim! I'm happily connected from home today...
:)
It was a long shot, but it worked. Very
C. Bensend [EMAIL PROTECTED] writes:
I had setup my pg_hba.conf originally like this:
host all all 10.15.0.0 255.255.255.0 trust
I was under the impression that the .0 was supposed to be equivalent to
a wildcard entry so that any connection from 10.15 would be able to
PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [ADMIN] pg_hba.conf
Hello,
I finally got it to work and as some have mentioned it was not the
encryption level.
I had setup my pg_hba.conf originally like this:
host all all 10.15.0.0 255.255.255.0 trust
I was under the impression
(Note: Please do not copy me individually on posts to the mailing
list. I do read the list and don't need two copies. Thanks.)
(Note2: I did Cc: this to LSanchez as she's yet to respond to any of
my prior comments, so I begin to suspect she's not getting/reading
the mailing list traffic?)
suggested tonight, as soon as I get home.
Thanks so much for your help!
Regards,
- Lily Anne
-Original Message-
From: Jim Seymour [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 27, 2004 10:03 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [ADMIN] pg_hba.conf
(Note: Please
] - [EMAIL PROTECTED]
AIM: marmstro2 - Jabber: [EMAIL PROTECTED]
-Original Message-
From: mike g [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 26, 2004 11:16 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [ADMIN] pg_hba.conf
Hello,
I finally got it to work and as some have
Thank you to all who replied with the additional info.
On Thu, May 27, 2004 at 09:35:06AM -0400, Tom Lane wrote:
C. Bensend [EMAIL PROTECTED] writes:
I had setup my pg_hba.conf originally like this:
host all all 10.15.0.0 255.255.255.0 trust
I was under the impression
PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [ADMIN] pg_hba.conf
Hello,
I believe I found my problem. The Cisco VPN client I use encrypts data
at a 168 bit level. Postgres only supports up to 128 bit correct?
Mike
On Tue, 2004-05-25 at 23:12, mike g wrote:
Hmm
Looks like I am still
[EMAIL PROTECTED] wrote:
Thanks Mike!
Do you know if pgSQL will be supporting higher level of encryption in
the near future? Most of us here at Ameritrade work from home via VPN.
We support SSL so you don't need VPN encryption. However, we should
work with whatever VPN encryption you are
26, 2004 12:51 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [ADMIN] pg_hba.conf
Hello,
I believe I found my problem. The Cisco VPN client I use encrypts data
at a 168 bit level. Postgres only supports up to 128 bit correct?
Mike
Thanks so much! :)
-Original Message-
From: Bruce Momjian [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 26, 2004 10:56 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: Re: [ADMIN] pg_hba.conf
[EMAIL PROTECTED] wrote:
Thanks Mike!
Do you
Note: Please do NOT Cc: me on replies to the mailing list. I read the
mailing list. One copy of your comments is sufficient. Thank you.
Thanks Mike!
Do you know if pgSQL will be supporting higher level of encryption in
the near future? Most of us here at Ameritrade work from home via
[EMAIL PROTECTED] (mike g) writes:
I believe I found my problem. The Cisco VPN client I use encrypts data
at a 168 bit level. Postgres only supports up to 128 bit correct?
That ought to be entirely irrelevant, as your VPN client would encrypt
all data going across the network, encrypted or
]
Subject: Re: [ADMIN] pg_hba.conf
[EMAIL PROTECTED] wrote:
Thanks Mike!
Do you know if pgSQL will be supporting higher level of encryption in
the near future? Most of us here at Ameritrade work from home via VPN.
We support SSL so you don't need VPN encryption. However, we should
I had setup my pg_hba.conf originally like this:
host all all 10.15.0.0 255.255.255.0 trust
I was under the impression that the .0 was supposed to be equivalent to
a wildcard entry so that any connection from 10.15 would be able to
connect. This was not so. By changing
[EMAIL PROTECTED] writes:
I already specified the IP address that was specified by my VPN
connection.
This is a long shot, but ... did you remember to SIGHUP the postmaster
after editing pg_hba.conf to allow that IP address?
regards, tom lane
Yes sir, did that, too.
Thanks,
- Lily Anne
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 25, 2004 10:50 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: Re: [ADMIN] pg_hba.conf
[EMAIL PROTECTED] writes:
I
that, too.
Thanks,
- Lily Anne
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 25, 2004 10:50 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: Re: [ADMIN] pg_hba.conf
[EMAIL PROTECTED] writes:
I already
Here it is
Thanks! :)
-Original Message-
From: Robert Treat [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 25, 2004 1:02 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [ADMIN] pg_hba.conf
I am thinking that the entry for this ip has an issue
Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 25, 2004 2:51 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: Re: [ADMIN] pg_hba.conf
[EMAIL PROTECTED] writes:
Here it is
host all all 10.29.15.0
: RE: [ADMIN] pg_hba.conf
Um, I restarted postmaster so many times already after I made the entry
and this is the only pg_hba.conf file in our server (you're right,
$PGDATA/pg_hba.conf). It's a brand new server that had just been built.
Have you tried connecting to your pgSQL server via VPN
[EMAIL PROTECTED] wrote:
Thanks Mike!
I already specified the IP address that was specified by my VPN
connection. I read through the docs and found nothing about anything
special with VPN connections.
Which address? The address at your end of the connection may not be
the same as the
PROTECTED]
Subject: Re: [ADMIN] pg_hba.conf
Your ip address range is probably different when connecting via a VPN
rather than in the office. By default postgres will not allow
connections from other locations even if tcpip_socket is true without
specifying an ip address range, database etc
special with VPN connections.
Regards,
- Lily Anne
-Original Message-
From: Mike G [mailto:[EMAIL PROTECTED]
Sent: Monday, May 24, 2004 10:23 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [ADMIN] pg_hba.conf
Your ip address range
Anne
-Original Message-
From: Robert Treat [mailto:[EMAIL PROTECTED]
Sent: Friday, May 21, 2004 8:04 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [ADMIN] pg_hba.conf
can you ping the server that postgresql is living on? or maybe your
misrepresenting the error message
On Thu, 2004-05-20 at 19:52, [EMAIL PROTECTED] wrote:
I'm trying to access our test postgreSQL server via VPN and even though
I already setup the host for the vpn's ip address, I'm still getting an
error similar to host for vpn address does not exist
What am I doing incorrectly?
The
Thanks Robert!
I did that as well and still didn't work. Any other ideas?
-Original Message-
From: Robert Treat [mailto:[EMAIL PROTECTED]
Sent: Friday, May 21, 2004 4:41 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [ADMIN] pg_hba.conf
On Thu, 2004-05-20 at 19:52, [EMAIL
, 2004 4:41 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [ADMIN] pg_hba.conf
On Thu, 2004-05-20 at 19:52, [EMAIL PROTECTED] wrote:
I'm trying to access our test postgreSQL server via VPN and even
though
I already setup the host for the vpn's ip address, I'm still getting
[EMAIL PROTECTED] writes:
I am trying to set up pg_hba.conf for PostgreSQL 7.3. I want to limit
access to a database from a host to the set of users in a file. The
documentation suggests that this is done as follows:
host dbname @user_file 10.0.1.12 255.255.255.255 md5
However, the
On Tue, Feb 03, 2004 at 12:48:34 -0600,
[EMAIL PROTECTED] wrote:
New to postgresql...I've done a lot of google-searching and searching of
the pgsql archives but haven't found much...
I'm trying to configure pg_hba.conf so that:
1. using a local connection, user postgres does not
Ganesan Kanavathy a écrit :
If I do any changes in pg_hba.conf file do I need restart pgsql.
The changes I made does not taking effect.
Hello,
The PostgreSQL documentation indicates that the pg_hba.conf file is read
on start-up and when the postmaster receives a SIGHUP signal. If you
edit the
Holger Jakobs [EMAIL PROTECTED] writes:
What about leaving it to the administrator of a system to provide a
function (either a C function in a shared lib or an executable) which
gets information passed and decides whether the access will be granted?
I think this is exactly what PAM is for.
On Wed, May 28, 2003 at 09:49:31 +0200,
Michael Mattox [EMAIL PROTECTED] wrote:
Is it possible to configure the pg_hba.conf to allow access from a dynamic
IP address? Or is it possible to allow ANY IP address? I tried using both
my domain name and *.*.*.* and neither work. I have a dynamic
host all192.168.0.0 255.255.0.0 trust
that should work, though it's pretty insecure. note you might need to
address your lan ip address if it's not 192.168.*.*
Robert Treat
On Thu, 2003-02-27 at 14:59, Sidar Lopez Cruz wrote:
how can i config this file to connect from any ip on my
Hi dan
IF possible i suggest to put a restriction from where your users come with
netwotk and mask.
I think that your solution is to complicate and suggest that all database is
owned by postgres with strong password and give your user full grant for a
single database.
so you haven't to manage a
On Thu, Nov 21, 2002 at 13:16:50 -0500,
Dan MacNeil [EMAIL PROTECTED] wrote:
Right now we give a user full privledges to the database, named after
the user by
1) creating the user with CREATEDB
2) Give the user the right to connect to the database dummy
3) creating a database as that
David Bear writes:
Also, since postgres starts as a windows service, how does one put commandline
parms on the postmaster so that it listens to a socket. Sorry about the
newbie questions but all the docs I found point to runing pg on various
unicies.
Consider reading the Administrator's
Thomas F. O'Connell wrote:
is there any way in postgres (7.1.3) to get postgres to source the
pg_hba.conf file without restarting the database completely?
will any new backend use a modified pg_hba.conf if it is modified while
postgres is running?
In 7.1.X and earlier, pg_hba.conf is
In 7.1.X and earlier, pg_hba.conf is reread on every connection request.
7.2.X will requires a sighup to the postmaster to reload pg_hba.conf.
why the change?
-tfo
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please
Thomas F. O'Connell wrote:
In 7.1.X and earlier, pg_hba.conf is reread on every connection request.
7.2.X will requires a sighup to the postmaster to reload pg_hba.conf.
why the change?
Performance. Faster to cache contents.
--
Bruce Momjian|
1 - 100 of 109 matches
Mail list logo
