From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Michael Fuhr <mike(at)fuhr(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: DH_check return value test correct? |
Date: | 2006-05-13 09:10:27 |
Message-ID: | 20060513091027.GJ12955@svana.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, May 12, 2006 at 09:05:55PM -0400, Tom Lane wrote:
> Michael Fuhr <mike(at)fuhr(dot)org> writes:
> > Incidentally, is it necessary to load the DH parameters anew and
> > call DH_check for every connection?
>
> We could maybe improve on that on Unix, but not so easily on Windows.
> Given the evidently nonexistent demand for this feature, I can't see
> putting any work into it ;-)
To be honest I'm not entirely sure of the benefits of allowing people
to specify the DH params. For the GnuTLS patch I just got the backend
to generate the params on postmaster start because I couldn't think if a
reason why you'd want to either use hard-coded values or user-specified
ones.
They're not security sensetive, knowing them doesn't help you crack the
stream. The client simply gets a copy of the server's parameters when
initiating the connection. What they do do it protect the security of
the stream if the private key has been comprimised. So we should use
EDH, but there's still no reason for the user to want to specify the
parameters...
Have a ncie day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2006-05-13 16:21:06 | Mention pg_dump version portability |
Previous Message | Martijn van Oosterhout | 2006-05-13 08:55:26 | Re: [GENERAL] Querying libpq compile time options |