Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id CBD6B632A26 for ; Sun, 1 Mar 2009 07:08:56 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 00471-06 for ; Sun, 1 Mar 2009 07:08:51 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from fmf.vtu.lt (fmf.vgtu.lt [193.219.145.206]) by mail.postgresql.org (Postfix) with ESMTP id 5B07A63561F for ; Sun, 1 Mar 2009 04:41:13 -0400 (AST) Received: from fmf.vgtu.lt (localhost [127.0.0.1]) by fmf.vtu.lt (Postfix) with ESMTP id 3CD851002F for ; Sun, 1 Mar 2009 10:37:26 +0200 (EET) Received: from 78.59.213.168 (SquirrelMail authenticated user nso) by fmf.vgtu.lt with HTTP; Sun, 1 Mar 2009 10:37:26 +0200 (EET) Message-ID: <60680.78.59.213.168.1235896646.squirrel@fmf.vgtu.lt> In-Reply-To: <281149.69937.qm@web23604.mail.ird.yahoo.com> References: <281149.69937.qm@web23604.mail.ird.yahoo.com> Date: Sun, 1 Mar 2009 10:37:26 +0200 (EET) Subject: Re: Postgesql and SSL From: "Lukas" To: pgsql-admin@postgresql.org Reply-To: Lukas@fmf.vtu.lt User-Agent: SquirrelMail/1.4.8 MIME-Version: 1.0 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-VGTU-MailScanner-OpenProtect-Information: Please contact the ISP for more information X-VGTU-MailScanner-OpenProtect: Found to be clean X-VGTU-MailScanner-OpenProtect-MCPCheck: X-VGTU-MailScanner-OpenProtect-From: lukas@fmf.vtu.lt 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: 200903/2 X-Sequence-Number: 31502 Hello again, nope, no use of it.. Situation stays the same.. Does any one have more ideas? -- Lukas UAB nSoft http://www.nsoft.lt Lukas at nsoft.lt +370 655 10 655 > You defo have all the required openssl headers and libs and configure > succeeds? It's a longshot, but I wonder if the prefix is somehow making > configure read the string wrong? I've never really needed to use prefix, > but what happend if you try > > ./configure --prefix='/DB' --with-openssl > > or perhaps > > ./configure --with-openssl --prefix=/DB > > > > --- On Sat, 28/2/09, Lukas wrote: > >> From: Lukas >> Subject: [ADMIN] Postgesql and SSL >> To: pgsql-admin@postgresql.org >> Date: Saturday, 28 February, 2009, 10:18 PM >> Hello, >> >> I am trying to run PostgreSQL with SSL, so I compiled and >> linked with >> options: >> >> ./configure --prefix=/DB --with-openssl >> >> Configured and installed successfully. >> In postgresql.conf I have option "ssl = on" >> When starting Postgres I get error: >> LOG: SSL is not supported by this build >> FATAL: invalid value for parameter "ssl": 1 >> DEBUG: proc_exit(1) >> DEBUG: shmem_exit(1) >> DEBUG: exit(1) >> >> Where is the problem? Is here versions which does not >> support SSL, it >> would be strange.. >> >> Versions used: >> PostgreSQL 8.3.4 >> OpenSSL 0.9.8j >> >> >> >> -- >> Lukas >> UAB nSoft >> http://www.nsoft.lt >> Lukas at nsoft.lt >> +370 655 10 655 >> >> >> >> >> -- >> This message has been scanned for viruses and >> dangerous content by >> OpenProtect(http://www.openprotect.com), and is >> believed to be clean. >> >> >> -- >> Sent via pgsql-admin mailing list >> (pgsql-admin@postgresql.org) >> To make changes to your subscription: >> http://www.postgresql.org/mailpref/pgsql-admin > > > > > -- > Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-admin > > -- > This message has been scanned for viruses and > dangerous content by OpenProtect(http://www.openprotect.com), and is > believed to be clean. > > -- This message has been scanned for viruses and dangerous content by OpenProtect(http://www.openprotect.com), and is believed to be clean.