<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On 4/25/2017 13:48, Karl Denninger wrote:<br>
<blockquote type="cite"
cite="mid:a529b468-ee65-c85a-3625-7dd7b0450681@denninger.net">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<p>I've been running pgpool-II for a very long time as a
connection pooler on a local host. It works very well.</p>
<p>Now I wish to use it across the Internet, potentially, which
introduces security concerns. Therefore I wish to have the
connection to the back end use SSL, while for the *on-same
machine* client connections I don't care and in fact I'd prefer
it be off (since otherwise you need to actually encrypt/decrypt
TWICE)</p>
<p>Is this supportable?</p>
<p>I turned ssl on but when I connect to pgpool the connection to
the server is NOT SSL-enabled, and I get an error because the
pg_hba.conf on the back end server is set to require ssl.</p>
<p>If I use psql directly to the server (with -h and -p) then it
works.</p>
<br>
</blockquote>
Indeed it was a brain fart; it appears that despite my attempt to
turn on openssl it didn't build with it, and having found that, it
is working.<br>
<br>
My apologies for the interruption. :-)<br>
<br>
<div class="moz-signature">-- <br>
Karl Denninger<br>
<a href="mailto:karl@denninger.net">karl@denninger.net</a><br>
<i>The Market Ticker</i><br>
<font size="-2"><i>[S/MIME encrypted email preferred]</i></font>
</div>
</body>
</html>