-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 30 Jun 2006 at 01:39 (-0400), Marcus Watts wrote:
I believe you're still barking up the wrong tree. The default realm is
just that, a default. If you really want to specify two different
realms, then that's fine -- that's why you can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[I apologize for the length of this, but it's about a problem that is
proving to be very inscrutable and it needs some explanation].
I'm doing some testing of code that authenticates against both an MIT K5
KDC and an Active Directory KDC. I've
On Jun 29, 2006, at 17:21, Mike Friedman wrote:
Any ideas about this? Is there any way to force connection to a
specific
KDC other than using the 'KRB5_CONFIG' environment variable? (We
don't
use SRV records here, so that's not an option even if it would help in
this case).
When a
Mike Friedman [EMAIL PROTECTED] writes:
Date: Thu, 29 Jun 2006 14:21:57 -0700 (PDT)
From: Mike Friedman [EMAIL PROTECTED]
To: kerberos@mit.edu
Subject: Is KRB5_CONFIG info cached?
In-Reply-To: [EMAIL PROTECTED]
...
[I apologize for the length of this, but it's about a problem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 29 Jun 2006 at 18:43 (-0400), Marcus Watts wrote:
As long as the KDCs are in different realms, you ought to be able to use
one context, and one KRB5_CONFIG file, to access both.
Marcus,
But each time I call my subroutine, I get a new
On Jun 29, 2006, at 19:41, Mike Friedman wrote:
If these KDCs are for two different realms, can you list both
config files in KRB5_CONFIG?
But then how do I get the *default realm* set correctly? In my
script, I do a parse_name() to create a principal object
corresponding to the TGS
Mike Friedman [EMAIL PROTECTED] writes:
...
So, at a closer look at Jeff Horwitz's code, looks like he expects
Authen::Krb5::init_context(). He's got this right before:
if (context) croak(Authen::Krb5 already initialized);
I ran into this problem a while back and contacted Jeff
