Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: binary
MIME-Version: 1.0
X-Mailer: MIME-tools 5.427 (Entity 5.427)
RT-Send-CC:
X-RT-Original-Encoding: iso-8859-1
Content-Length: 1246

[hartmans - Fri Feb 17 15:50:25 2012]:

> I would support reporting these errors via KRB5_TRACE.
> I would not support
> 
> 1) changing context initialization to fail in cases where it currently
> does not
> 
> 2) Reporting these erros to STDERR, system loging, event viewer or the
> like.


The plan is to support trace logging via KRB5_TRACE. The section and  subsection of the 
configuration file where the error was found together with the error code will be reported.

We're also considering an option of eliminating the "loose" context initialization.  The current 
relation between the requirements  stated in the configuration file and what is really 
happening during the library context initialization is conflicting and misleading.  We do read 
the values from the configuration, but, in several cases, do not check the return codes from 
profile_get_  functions.  If one cares enough about some configuration parameters to read 
them from the configuration files while initializing library context, it should be guaranteed 
that these values are not ignored or misinterpreted, rather are retrieved and processed 
correctly, without hidden surprises.

We do not plan on reporting "these erros to STDERR, system loging, event viewer".