Re: Logging of matching pg_hba.conf entry during auth skips trust auth, potential security issue
От | Jacob Champion |
---|---|
Тема | Re: Logging of matching pg_hba.conf entry during auth skips trust auth, potential security issue |
Дата | |
Msg-id | CAAWbhmjZ0OFvZ79i9cn7nNBHG_L5SWaBMz+NUi0qbZr4mVbjZQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Logging of matching pg_hba.conf entry during auth skips trust auth, potential security issue (Stephen Frost <sfrost@snowman.net>) |
Ответы |
Re: Logging of matching pg_hba.conf entry during auth skips trust auth, potential security issue
|
Список | pgsql-hackers |
On Thu, Aug 17, 2023 at 9:01 AM Stephen Frost <sfrost@snowman.net> wrote: > That doesn't seem quite right ... admittedly, 'trust' isn't performing > authentication but there can certainly be an argument made that the > basic 'matched a line in pg_hba.conf' is a form of authentication I'm not personally on board with this argument, but... > and > worse really, saying 'not authenticated' would seem to imply that we > didn't allow the connection when, really, we did, and that could be > confusing to someone. ...with this one, I agree. > Maybe 'connection allowed' instead..? Hm. It hasn't really been allowed yet, either. To illustrate what I mean: LOG: connection received: host=[local] LOG: connection allowed: user="jacob" method=trust (/home/jacob/src/data/pg16/pg_hba.conf:117) LOG: connection authorized: user=jacob database=postgres application_name=psql Maybe "unauthenticated connection:"? "connection without authentication:"? "connection skipped authentication:"? --Jacob
В списке pgsql-hackers по дате отправления: