Re: BUG #4340: SECURITY: Is SSL Doing Anything?
От | Dan Kaminsky |
---|---|
Тема | Re: BUG #4340: SECURITY: Is SSL Doing Anything? |
Дата | |
Msg-id | 48AAFD0F.6040503@doxpara.com обсуждение исходный текст |
Ответ на | Re: BUG #4340: SECURITY: Is SSL Doing Anything? (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: BUG #4340: SECURITY: Is SSL Doing Anything?
|
Список | pgsql-bugs |
Tom Lane wrote: > Dan Kaminsky <dan@doxpara.com> writes: > >> My question has been: When you attempt to create an SSL connection to >> database.backend.com, do you actually validate that: >> > > >> 1) The subject name of the certificate you're connecting to is >> database.backend.com, and >> 2) At least the basic checks (expiration, chaining back to a valid root) >> occur? >> > > [ shrug... ] We do whatever OpenSSL's default validation behavior is. > If that's inadequate you probably ought to be taking it up with them, > instead of trying to get downstream projects to fix it one at a time. > > regards, tom lane > Heh, you're the one making guarantees to your users. I'm just asking the exact nature of those guarantees. I agree that #2 is entirely under the control of OpenSSL -- but I'd like to know if #1 is being satisfied, i.e. OpenSSL knows you're looking to validate database.backend.com as opposed to "some cert that chains back", which is a worthless security assertion. --Dan
В списке pgsql-bugs по дате отправления: