MIME-Version: 1.0
In-Reply-To: <4DC575F6.4060508@kerneljack.com>
References: <4DC575F6.4060508@kerneljack.com>
Date: Sat, 7 May 2011 19:46:04 +0200
Message-ID: <BANLkTim+=1zT5=4y-ymjAyREvZ5LBX0Fcw@mail.gmail.com>
Subject: Re: Error in SSL config documentation?
From: Magnus Hagander <magnus@hagander.net>
To: Khusro Jaleel <mailing-lists@kerneljack.com>
Cc: pgsql-docs@postgresql.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Sat, May 7, 2011 at 18:40, Khusro Jaleel
<mailing-lists@kerneljack.com> wrote:
> Hello, according to section 17.8.1 of the docs, I have added "clientcert"=
 to
> a hostssl line in my pg_hba.conf file, but upon restart of the server, I'=
m
> getting the following error and the server fails to start up:
>
> LOG: =A0invalid authentication method "clientcert"
> CONTEXT: =A0line 82 of configuration file
> "/var/lib/pgsql/9.0/data/pg_hba.conf"
> FATAL: =A0could not load pg_hba.conf
>
> Changing the "clientcert" to "cert" seems to work. So does this mean the
> documentation is incorrect?

These are two different things.

as the docs say, "The clientcert option in pg_hba.conf is available
for all authentication methods, but only for rows specified as
hostssl.", and a bit further down "If you are setting up client
certificates, you may wish to use the cert authentication method, so
that the certificates control user authentication as well as providing
connection security. "


cert is the authentication method that uses client certificates to log in.


clientcert=3D1 makes the server request a client certificate - but does
not use it for authentication. So the client just has to present *any
valid* client certificate, and can then use whatever other
authenticaiton method is specified (md5, ldap, etc).


--=20
=A0Magnus Hagander
=A0Me: http://www.hagander.net/
=A0Work: http://www.redpill-linpro.com/