Skip site navigation (1) Skip section navigation (2)

Re: [PATCH] Remove useless DH param code on client side

From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: [PATCH] Remove useless DH param code on client side
Date: 2006-04-12 14:09:12
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-patches
On Wed, Apr 12, 2006 at 10:00:29AM -0400, Tom Lane wrote:
> Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> > It's not clear why the code was added in the first place,
> I thought it was there to support client-side authentication (ie,
> verifying the server's certificate).  We don't support that right
> now but we ought to.

That's there AFAICS, using the functions:

SSL_CTX_load_verify_locations(SSL_context, fnbuf, NULL)
SSL_CTX_set_verify(SSL_context, SSL_VERIFY_PEER, verify_cb)

That has nothing to do with DH params though, which are purely used to
generate a secret key during negotiation. The server sends you the DH
params as part of the negotiation, the client doesn't need any itself.

Have a nice day,
Martijn van Oosterhout   <kleptog(at)svana(dot)org>
> Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
> tool for doing 5% of the work and then sitting around waiting for someone
> else to do the other 95% so you can sue them.

In response to

pgsql-patches by date

Next:From: Kris JurkaDate: 2006-04-12 22:57:25
Subject: pg_dump insert transactions
Previous:From: Tom LaneDate: 2006-04-12 14:00:29
Subject: Re: [PATCH] Remove useless DH param code on client side

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group