On Thu, Dec 5, 2013 at 11:44 PM, Ian Harding <harding....@gmail.com> wrote: > > My naviserver nsdbipg module seems to barf on it. > psql connects fine.
nsbipg is configured with a datasource param which lets you pass any key=value pairs directly through to libpq. According to: http://www.postgresql.org/docs/current/static/libpq-connect.html#LIBPQ-PARAMKEYWORDS ...the default sslmode is prefer, which apparently means "don't bother trying". You actually need sslmode=require. nsdbpg unfortunately implements it's own datasource parsing so you're stuck with user:host:db Are you also using nsssl? Looks like some modifications are required: http://www.postgresql.org/docs/9.3/static/libpq-ssl.html#LIBPQ-SSL-INITIALIZE If your application initializes libssl and/or libcrypto libraries and libpq is built with SSL support, you should call PQinitOpenSSL to tell libpq that the libssl and/or libcrypto libraries have been initialized by your application, so that libpq will not also initialize those libraries. But you could try connecting to the db via ssl with nsssl unloaded, to confirm that it works. Not sure what the best way is to coordinate with nsssl who should init the openssl library. ------------------------------------------------------------------------------ Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk _______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
