On Wed, 12 Nov 2014, Todd Grayson wrote: > Hi, > > I've been searching around looking for clear discussion around how to > enable (debug) logging on windows, for the MIT Kerberos for Windows. I > found the following discussion in the release notes for the kfw 3.2.2, > which stated the following: > > http://web.mit.edu/kerberos/kfw-3.2/kfw-3.2.2/relnotes.html > > Under "Release History > 3.2.0 > Integrated Logon Improvements" > > > - Add a debugging mode which when activated logs to the Windows > Application Event Log. [HKLM\System\CurrentControlSet\Services\MIT > Kerberos\NetworkProvider] > DWORD "Debug" > > > > To clarify, is this the proper detailed description for what is being > stated there: > > HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MIT > Kerberos\NetworkProvider > Registry Value: Debug > Value Type: REG_DWORD > Value Data: 0x1 > (e.g. set to 1 to enable debug) > > If so; Does this registry setting to enable debug hold true for kfw 4.0.1 > as well?
The relevant pieces of code appear to remain present in KfW 4.0.1. However, since KfW 4.0.x is based off of krb5 1.10.x, which supports the KRB5_TRACE environment variable, I would expect the latter to be more useful in real-world debugging situations. -Ben ________________________________________________ Kerberos mailing list Kerberos@mit.edu https://mailman.mit.edu/mailman/listinfo/kerberos
