X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id B6756528FA for ; Mon, 8 Aug 2005 12:55:30 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 99326-09 for ; Mon, 8 Aug 2005 15:55:28 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 59BD952E2C for ; Mon, 8 Aug 2005 12:55:26 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j78FsxEY028928; Mon, 8 Aug 2005 11:54:59 -0400 (EDT) To: Mario Soto Cordones - Venezuela Cc: alvherre@alvh.no-ip.org, pgsql-admin@postgresql.org Subject: Re: [GENERAL] postgresql Secure Mode In-reply-to: References: <20050808135640.GB26568@alvh.no-ip.org> <20050808143851.GA26979@alvh.no-ip.org> <20050808151811.GA28073@alvh.no-ip.org> Comments: In-reply-to Mario Soto Cordones - Venezuela message dated "Mon, 08 Aug 2005 11:41:24 -0400" Date: Mon, 08 Aug 2005 11:54:59 -0400 Message-ID: <28927.1123516499@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200508/86 X-Sequence-Number: 18405 Mario Soto Cordones - Venezuela writes: > LOG Say: > LOG: conexión recibida: host=192.168.0.100 port=1175 > FATAL: no hay una línea en pg_hba.conf para «192.168.0.100», > usuario «vasa», base de datos «vasa», SSL inactivo > LOG: conexión recibida: host=192.168.0.100 port=1226 > FATAL: no hay una línea 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