Re: Support for NSS as a libpq TLS backend
От | Michael Paquier |
---|---|
Тема | Re: Support for NSS as a libpq TLS backend |
Дата | |
Msg-id | YBOkxETLk5KZ8yvX@paquier.xyz обсуждение исходный текст |
Ответ на | Re: Support for NSS as a libpq TLS backend (Daniel Gustafsson <daniel@yesql.se>) |
Ответы |
Re: Support for NSS as a libpq TLS backend
|
Список | pgsql-hackers |
On Fri, Jan 29, 2021 at 12:20:21AM +0100, Daniel Gustafsson wrote: > SSL is admittedly an obsolete technical term, but it's one that enough people > have decided is interchangeable with TLS that it's not a hill worth dying on > IMHO. Since postgres won't allow for using libnss or OpenSSL for cryptohash > *without* compiling SSL/TLS support (used or not), I think --with-ssl=LIB is > more descriptive and less confusing. Okay, let's use --with-ssl then for the new switch name. The previous patch is backward-compatible, and will simplify the rest of the set, so let's move on with it. Once this is done, my guess is that it would be cleaner to have a new patch that includes only the ./configure and MSVC changes, and then the rest: test refactoring, cryptohash, strong random and lastly TLS (we may want to cut this a bit more though and perhaps have some restrictions depending on the scope of options a first patch set could support). I'll wait a bit first to see if there are any objections to this change. -- Michael
Вложения
В списке pgsql-hackers по дате отправления: