Re: BUG #1001: Inconsistent authentication between psql and PQconnectdb - possible security implications?
От | Bruno Wolff III |
---|---|
Тема | Re: BUG #1001: Inconsistent authentication between psql and PQconnectdb - possible security implications? |
Дата | |
Msg-id | 20031205173035.GA16741@wolff.to обсуждение исходный текст |
Ответ на | BUG #1001: Inconsistent authentication between psql and PQconnectdb - possible security implications? ("PostgreSQL Bugs List" <pgsql-bugs@postgresql.org>) |
Список | pgsql-bugs |
On Fri, Dec 05, 2003 at 12:47:58 -0400, PostgreSQL Bugs List <pgsql-bugs@postgresql.org> wrote: > > All is well with psql authentication. However, when I tried to > use knoda/hk_classes to access the database, I could not get authenticated. A typical error message was IDENT authenticationfailed for user "irwin". When I traced this down through the hk_classes code it was using PQconnectdb to connnectto the database, and there were complaints in the postgresql log that the identd server was not available. All knoda/hk_classes/PQconnectdbproblems disappeared when I installed identd (apt-get install pidentd) on my Debian stable system. So all seems well when identd is installed, but there may be a security concern with psql when it is not. On theother hand, if psql is actually secure when identd is not running, then why isn't PQconnectdb using the exact same (secure)method of authentication for this case? When connecting using domain sockets the local equivalent of getpeeruid is used to determine which user is connecting rather than by asking an ident server. When you use a network socket, then the user is checked by asking the ident server at the same IP address as the connection is coming from.
В списке pgsql-bugs по дате отправления: