Skip site navigation (1) Skip section navigation (2)

Re: GSSAPI doesn't play nice with non-canonical host names

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: GSSAPI doesn't play nice with non-canonical host names
Date: 2008-01-30 22:27:07
Message-ID: 24324.1201732027@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> 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?

Yeah, I found it:
https://bugzilla.redhat.com/show_bug.cgi?id=430983

The best fix is not entirely clear, but in any case it's not our bug.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Decibel!Date: 2008-01-30 22:58:48
Subject: Re: [PATCHES] Better default_statistics_target
Previous:From: Simon RiggsDate: 2008-01-30 22:10:21
Subject: Re: Will PostgreSQL get ported to CUDA?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group