X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id DD368D1B349 for ; Wed, 26 May 2004 07:48:23 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 95499-09 for ; Wed, 26 May 2004 07:48:05 -0300 (ADT) Received: from jimsun.LinxNet.com (jimsun.linxnet.com [64.32.196.134]) by svr1.postgresql.org (Postfix) with ESMTP id 0315FD1B341 for ; Wed, 26 May 2004 07:48:02 -0300 (ADT) Received: by jimsun.LinxNet.com (Postfix, from userid 332) id CE353430E; Wed, 26 May 2004 06:48:04 -0400 (EDT) To: pgsql-admin@postgresql.org Subject: Re: pg_hba.conf Reply-To: pgsql-admin@postgresql.org Message-Id: <20040526104804.CE353430E@jimsun.LinxNet.com> Date: Wed, 26 May 2004 06:48:04 -0400 (EDT) From: jseymour@LinxNet.com (Jim Seymour) X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200405/270 X-Sequence-Number: 13586 > > 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? That's your VPN's end-to-end/network-to-network connectivity. It has nothing to do with PostgreSQL at all. (Note: Please do NOT copy me on replies. I do read the mailing list.) Jim