Re: Support for NSS as a libpq TLS backend
От | Heikki Linnakangas |
---|---|
Тема | Re: Support for NSS as a libpq TLS backend |
Дата | |
Msg-id | 7ed636a0-872c-3ea7-dc44-b35dd515bb87@iki.fi обсуждение исходный текст |
Ответ на | 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 27/10/2020 22:07, Daniel Gustafsson wrote: > /* > * Track whether the NSS database has a password set or not. There is no API > * function for retrieving password status, so we simply flip this to true in > * case NSS invoked the password callback - as that will only happen in case > * there is a password. The reason for tracking this is that there are calls > * which require a password parameter, but doesn't use the callbacks provided, > * so we must call the callback on behalf of these. > */ > static bool has_password = false; This is set in PQssl_passwd_cb function, but never reset. That seems wrong. The NSS database used in one connection might have a password, while another one might not. Or have I completely misunderstood this? - Heikki
В списке pgsql-hackers по дате отправления: