Re: GSSAPI doesn't play nice with non-canonical host names
От | Magnus Hagander |
---|---|
Тема | Re: GSSAPI doesn't play nice with non-canonical host names |
Дата | |
Msg-id | 20080128132510.GE26468@svr2.hagander.net обсуждение исходный текст |
Ответ на | Re: GSSAPI doesn't play nice with non-canonical host names (Stephen Frost <sfrost@snowman.net>) |
Ответы |
Re: GSSAPI doesn't play nice with non-canonical host names
Re: GSSAPI doesn't play nice with non-canonical host names |
Список | pgsql-hackers |
On Sun, Jan 27, 2008 at 09:32:54PM -0500, Stephen Frost wrote: > > > While I'm complaining: that's got to be one of the least useful error > > messages I've ever seen, and it's for a case that's surely going to be > > fairly common in practice. Can't we persuade GSSAPI to produce > > something more user-friendly? At least convert "7" to "Server not > > found in Kerberos database"? > > I agree, and have found it to be very frustrating while working w/ > Kerberos in general. I *think* there's a library which can convert > those error-codes (libcomm-err?), but I've not really looked into it > yet. AFAIK, that one is for Kerberos only. For GSSAPI, we already use the gss_display_status function to get the error messages. I think the problem here is in the Kerberos library? //Magnus
В списке pgsql-hackers по дате отправления: