-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 13 Jan 2009 at 13:29 (-0500), Ken Hornstein wrote:
> May I humbly suggest that maybe, just maybe, for something like you KDC > you NOT rely on some pre-compiled binary compiled by god-knows-who with > god-knows-what options? Judging by what you're posting, something seems > to be majorly wrong here ... at least with error reporting. > > (And at the very least, you could always compile with debugging turned > on to try to track down the problem). Ken, I couldn't agree more! In fact, I made this point yesterday at a meeting where the person who installed this KDC was present. I was emphatic that I would never run a production KDC like this, especially since over the years I've found it necessary either to modify the compile time configuration, or, more commonly, to troubleshoot problems like this. But, in fairness, this was intended to be a test KDC with very limited use and it has been working thus far, used by just one of my colleagues to test his applications that do basic admin functions, where the aforementioned problems have not arisen. I think I may have to do my current testing elsewhere, rather than trying to get this KDC functioning properly. Thanks. Mike _________________________________________________________________________ Mike Friedman Information Services & Technology mi...@berkeley.edu 2484 Shattuck Avenue 1-510-642-1410 University of California at Berkeley http://mikef.berkeley.edu http://ist.berkeley.edu _________________________________________________________________________ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkls37gACgkQFgKSfLOvZ1QjugCbBhVMIuSayZKM1ie88a4C5qNz 2RoAni7KN0Lq78veaN7ol7JvQrNBMcNX =bLrU -----END PGP SIGNATURE----- ________________________________________________ Kerberos mailing list Kerberos@mit.edu https://mailman.mit.edu/mailman/listinfo/kerberos
