[22968] in Kerberos
Re: Generic unknown RC/IO error while verifying initial ticket
daemon@ATHENA.MIT.EDU (Sam Hartman)
Wed Dec 1 17:21:32 2004
To: Ezra Peisach <epeisach@mit.edu>
From: Sam Hartman <hartmans@mit.edu>
Date: Wed, 01 Dec 2004 17:20:22 -0500
In-Reply-To: <200412011922.iB1JMM5f002711@contents-vnder-pressvre.mit.edu>
(Ezra Peisach's message of "Wed, 1 Dec 2004 14:22:22 -0500 (EST)")
Message-ID: <tslmzwxslsp.fsf@cz.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
cc: kerberos@mit.edu
Errors-To: kerberos-bounces@mit.edu
>>>>> "Ezra" == Ezra Peisach <epeisach@MIT.EDU> writes:
Ezra> Hmm - without much code changes from the external API....
Ezra> a) There could be a new function
Ezra> krb5_get_extended_error_text - or something like that - to
Ezra> retreive the extended message...
Ezra> b) There would be an equivalent function to create an
Ezra> extended error message. (thread specific context?)
I was thinking of sticking this in the krb5 context as Heimdal does.
Ezra> c) When the error table is initialized - install a
Ezra> com_err_proc that will query the extended error and format
Ezra> it nicely. If an extended error is not present - don't
Ezra> display.
That seems problematic.
There are some issues to be worked out to make sure we don't prevent
people from localizing our errors, but the basic approach seems
doable.
--Sam
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
