Skip site navigation (1) Skip section navigation (2)

Re: BUG #5008: Server Startup Problem - When server is configured for SSL

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Jalaj Negi <jalajsinghnegi(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #5008: Server Startup Problem - When server is configured for SSL
Date: 2009-08-27 15:45:41
Message-ID: 9837222c0908270845u7043bcebu5efb33caa3a14efb@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
2009/8/27 Jalaj Negi <jalajsinghnegi(at)gmail(dot)com>:
> Hi,
> I tried by setting the requirement for certificates only on non-localhost addresses. It works perfectly fine in that case.
> Whats the solution in case of requesting client certificates on localhost connection?
>
> One temporary solution I found for above question is to set PGSSLCERT, PGSSLKEY, PGSSLROOTCERT, PGSSLCRL
> as system environment variables and let them point to valid client certificate, key, root certificate and crl. Then I rebooted
> my windows machine and database server started perfectly fine.
> Is this solution fine or some fix is needed in code?

I think that qualifies as a workaround, but we need to find a proper
solution. If that takes an API change (the discussions about a "ping"
function), that's not going to be until 8.5 though.

-- 
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

In response to

pgsql-bugs by date

Next:From: Alvaro HerreraDate: 2009-08-27 15:46:46
Subject: Re: BUG #4996: postgres.exe memory consumption keeps going up
Previous:From: Alvaro HerreraDate: 2009-08-27 15:43:36
Subject: Re: fillfactor hides autovacuum parameters in 8.4.0

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group