Re: [PATCH v6] GSSAPI encryption support
От | David Steele |
---|---|
Тема | Re: [PATCH v6] GSSAPI encryption support |
Дата | |
Msg-id | 56E05575.9060200@pgmasters.net обсуждение исходный текст |
Ответ на | [PATCH v6] GSSAPI encryption support (Robbie Harwood <rharwood@redhat.com>) |
Ответы |
Re: [PATCH v6] GSSAPI encryption support
Re: [PATCH v6] GSSAPI encryption support |
Список | pgsql-hackers |
Hi Robbie, On 3/8/16 5:44 PM, Robbie Harwood wrote: > Hello friends, > > Here's yet another version of GSSAPI encryption support. It's also > available for viewing on my github: I got this warning when applying the first patch in the set: ../other/v6-0001-Move-common-GSSAPI-code-into-its-own-files.patch:245: new blank line at EOF. + warning: 1 line adds whitespace errors. I know it's minor but I'm always happier when patches apply cleanly. The build went fine but when testing I was unable to logon at all. I'm using the same methodology as in http://www.postgresql.org/message-id/56BE0FF9.70302@pgmasters.net except that I'm running against 51c0f63 and using the v6 patch set. psql simply hangs and never returns. I have attached a pcap of the psql/postgres session generated with: tcpdump -i lo -nnvvXSs 1514 port 5432 -w gssapi.pcap If you would like me to capture more information please let me know specifically how you would like me to capture it. I reverted to v5 and got the same behavior I was seeing with v4 and v5, namely that I can only logon occasionally and usually get this error: psql: expected authentication request from server, but received Using a fresh build from 51c0f63 I can logon reliably every time so I don't think there's an issue in my environment. -- -David david@pgmasters.net
Вложения
В списке pgsql-hackers по дате отправления: