Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 0178D64FC39 for ; Thu, 30 Oct 2008 00:26:34 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 82164-06 for ; Thu, 30 Oct 2008 00:26:31 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.28]) by postgresql.org (Postfix) with ESMTP id 4EACC64FC2A for ; Thu, 30 Oct 2008 00:26:31 -0300 (ADT) Received: by yx-out-2324.google.com with SMTP id 8so122645yxb.73 for ; Wed, 29 Oct 2008 20:26:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=ZaFDIAYa47qaHo4J+Uuo7TF+zJ3ZY97UoOR+UUe4zWA=; b=ZJQJj8C+AcupwOub/sAfwAeHAbwOJjZekWRYxC2WpPaK3WC0vctfJZHdyc0bowb6zc epwUQ5K6WRWLlzvdQhJv0mD0h3wY4O12X8Ao7JwIW25t0WZJUrLxqdl9SMoyDINEzMQj uKSFIcEqUZfhCwiwg2MPfqsCO26Q0e5YkymmY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=mqX9f/0deE4t1PIjzFDHA356rohVkTIFZax3JYkFMC53LgDrjYHDLGSVIGIoa+tEu6 iH3d3PzTsM7LVJmIVMizWhLHHjHEreApq/JQQdwCIMilQkaj+2IxFo59IxTCXWYZXUrh BMlNOkLwbtKQ+ir1tQqS+q1eiUUbP88t/uYmQ= Received: by 10.151.9.1 with SMTP id m1mr2678802ybi.199.1225337190762; Wed, 29 Oct 2008 20:26:30 -0700 (PDT) Received: by 10.150.182.7 with HTTP; Wed, 29 Oct 2008 20:26:30 -0700 (PDT) Message-ID: <4544e0330810292026j1b8e9307j62d6a9c828c7a6b5@mail.gmail.com> Date: Wed, 29 Oct 2008 22:26:30 -0500 From: "Peter Koczan" To: "Tom Lane" Subject: Re: SSL and md5 password? Cc: "Alvaro Herrera" , "Scott Marlowe" , "pgsql-admin@postgresql.org" In-Reply-To: <2764.1225332660@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4544e0330810291007p5b68fba2o4ee782b4d4f92878@mail.gmail.com> <20081029185434.GH4331@alvh.no-ip.org> <2764.1225332660@sss.pgh.pa.us> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200810/177 X-Sequence-Number: 30633 On Wed, Oct 29, 2008 at 1:49 PM, Scott Marlowe wrote: > According to this, you're trying to connect with SSL off, right? I > don't think you've got any matching lines for that in your > pg_hba.conf. But I could be reading that wrong. Well, psql is trying to connect with SSL off even though postgres was built with SSL support, the server has SSL turned on, and psql connects with SSL by default for Kerberos connections. Where I was getting confused was that, for some reason, md5 authentication wasn't using SSL (or at least that's what the error suggested) and the only thing I changed was what user/auth-method I was using. On Wed, Oct 29, 2008 at 9:11 PM, Tom Lane wrote: > Alvaro Herrera writes: >> libpq tries to connect with SSL on and then falls back to SSL off. If >> the latter fails, the error message from the first attempt has been >> overwritten, and only the second one is logged. >> This has been fixed by Magnus on CVS HEAD. > > Right. So in the meantime, what Peter should do is try the problem case > after > export PGSSLMODE=require > so that he can see the error message that's relevant to his desired use. After exporting that environment variable, it works. Thanks. Peter