Actually, postgresql.conf already has ssl set to off, but there was
one line that has sslhost in the pg_hba.conf file. It shouldn't have
mattered because it wasn't a range of IP's that exists, but I
commented it out anyway. I stopped and restarted postgres and it made
no difference.
Carol
On Jul 15, 2009, at 2:22 PM, Chander Ganesan wrote:
Carol Walter wrote:
Well, that is a definite possibility. When I try to log in to the
8.2.10. instance from another machine on our network, I get an
authentication error. The error log says that authentication is
failing but it doesn't say why. When I originally put this 8.2.10
instance up, I was testing enabling ssl. It's possible that
somehow I got ssl partially configured, and that's confusing
postgres. The reason I scrapped the upgrade to 8.2.10 from 8.2.4
was that I decided to go to 8.3.6 instead. When I really did
enable ssl there, I had some problems getting the certs to work
correctly, but I got ssl errors in the error log. Anyway, you say
that I should be able to get 8.2.10 working if I have to drop back
to that. I may just have to take the ssl bits out and reinstall
the whole thing.
Why not just set "ssl=no" (or comment out the line) in your
postgresql.conf and remove any 'hostssl' lines from your pg_hba.conf
file. That will effectively disable SSL. IIRC There's really no
need to rebuild/reinstall anything..
--
Chander Ganesan
Open Technology Group, Inc.
One Copley Parkway, Suite 210
Morrisville, NC 27560
919-463-0999/877-258-8987
http://www.otg-nc.com
Expert PostgreSQL, PostGIS & other Open Source training delivered
worldwide.
--
Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
