| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Mario Soto Cordones - Venezuela <msotocl(at)gmail(dot)com> |
| Cc: | alvherre(at)alvh(dot)no-ip(dot)org, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: [GENERAL] postgresql Secure Mode |
| Date: | 2005-08-08 15:54:59 |
| Message-ID: | 28927.1123516499@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
Mario Soto Cordones - Venezuela <msotocl(at)gmail(dot)com> writes:
> LOG Say:
> LOG: conexin recibida: host=192.168.0.100 port=1175
> FATAL: no hay una lnea en pg_hba.conf para 192.168.0.100,
> usuario vasa, base de datos vasa, SSL inactivo
> LOG: conexin recibida: host=192.168.0.100 port=1226
> FATAL: no hay una lnea en pg_hba.conf para 192.168.0.100,
> usuario vasa, base de datos vasa, SSL inactiv
> but SSl its active
What that's showing is that the client isn't trying to use SSL. So
either you have client-side code that's not SSL-aware at all, or the
configuration problem is on the client side.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2005-08-08 16:08:44 | Re: [GENERAL] postgresql Secure Mode |
| Previous Message | Mario Soto Cordones - Venezuela | 2005-08-08 15:41:24 | Re: [GENERAL] postgresql Secure Mode |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nigel Horne | 2005-08-08 16:06:03 | Updating timestamps |
| Previous Message | Martín Marqués | 2005-08-08 15:52:19 | Re: PL/pgSQL in 8.0 |