Re: ssl

From: "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pg <pg(at)newhonest(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: ssl
Date: 2003-03-19 14:43:45
Message-ID: Pine.LNX.4.21.0303191439070.10824-100000@ponder.fairway2k.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, 19 Mar 2003, Tom Lane wrote:

> "Nigel J. Andrews" <nandrews(at)investsystems(dot)co(dot)uk> writes:
> > I must say my non rpm installation doesn't seem to pick up the hostssl line in
> > pg_hba. Or at least it doesn't match it when a connection comes in. I didn't
> > get very far into looking into that so it's probably something I'm doing wrong.
>
> > FWIW, my pg_hba entry is:
> > hostssl all all xx.xx.xx.xx 255.255.255.240 md5
> > and the error I get is:
> > FATAL: No pg_hba.conf entry for host xx.xx.xx.xx, user vtc, database vtc
>
> I believe it would act that way if the incoming connection is non-SSL
> (which suggests that your libpq isn't compiled with SSL support).

Interesting you should say that because I know remember what happened, slap me
with a wet fish later for the noise.

I'm convinced I rebuilt on the workstation in order to get a libpq with ssl. I
am equally convinced I tested it and it worked. Then a couple of days later
trying to get the developers using Windows to be able to connect I looked at it
again and I found my psql was no longer linked against the ssl library. Was
very wierd.

However, I never was able to get the developers connected. I may need to
revisit that later.

Sorry for the noise, my memory is going.

--
Nigel Andrews

In response to

  • Re: ssl at 2003-03-19 14:32:11 from Tom Lane

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2003-03-19 14:56:55 Re: vacuum full fills up disk
Previous Message greg 2003-03-19 14:41:00 Re: insert aliases?