DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.uk;
	h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
	b=1PeyJwQp6sV6oJ9tvgKPfVGEdT19RIBnNiLE5STFUxR9OS/8s7zF+O72Do+iKMKPwR4r0N4oMS7WDn0guYSjrYk6KE9RlBIILzGaen3zk/D3HCvgXswJmEKXl6A8R7/C9wfAZGp48N35B8UaHC877U2zgZX94+22PPyWT4QokCg=;
Date: Sun, 1 Mar 2009 12:49:51 +0000 (GMT)
From: Glyn Astill <glynastill@yahoo.co.uk>
Reply-To: glynastill@yahoo.co.uk
Subject: Re: Postgesql and SSL
To: pgsql-admin@postgresql.org, Lukas@fmf.vtu.lt
In-Reply-To: <60680.78.59.213.168.1235896646.squirrel@fmf.vgtu.lt>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-ID: <807164.51612.qm@web23602.mail.ird.yahoo.com>

have you generated the ssl certificates too?


--- On Sun, 1/3/09, Lukas <Lukas@fmf.vtu.lt> wrote:

> From: Lukas <Lukas@fmf.vtu.lt>
> Subject: Re: [ADMIN] Postgesql and SSL
> To: pgsql-admin@postgresql.org
> Date: Sunday, 1 March, 2009, 8:37 AM
> Hello again,
>=20
>  nope, no use of it.. Situation stays the same.. Does any
> one have more
> ideas?
>=20
>=20
> --
> Lukas
> UAB nSoft
> http://www.nsoft.lt
> Lukas at nsoft.lt
> +370 655 10 655
>=20
>=20
> > 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=3D'/DB' --with-openssl
> >
> > or perhaps
> >
> > ./configure --with-openssl  --prefix=3D/DB
> >
> >
> >
> > --- On Sat, 28/2/09, Lukas <Lukas@fmf.vtu.lt>
> wrote:
> >
> >> From: Lukas <Lukas@fmf.vtu.lt>
> >> 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=3D/DB --with-openssl
> >>
> >> Configured and installed successfully.
> >> In postgresql.conf I have option "ssl =3D
> 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.
> >
> >
>=20
>=20
>=20
> --=20
> This message has been scanned for viruses and
> dangerous content by
> OpenProtect(http://www.openprotect.com), and is
> believed to be clean.
>=20
>=20
> --=20
> Sent via pgsql-admin mailing list
> (pgsql-admin@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin=0A=0A=0A