I'm glad more was asked about this subject, I gained more understanding of
how this should work. In this case, the gss_init_sec_context failed trying
to get a cross-realm tgt using MSLSA ccache but has no problem if I used
API:krb5cc ccache. the realm info is more explict in krb5.ini but I
peter huang wrote:
I'm glad more was asked about this subject, I gained more understanding of
how this should work. In this case, the gss_init_sec_context failed trying
to get a cross-realm tgt using MSLSA ccache but has no problem if I used
API:krb5cc ccache. the realm info is more
You can use the current release of MIT Krb5. I don't remember seeing
this issue at all when I was performing gss-interop testing on Windows.
Jeffrey Altman
peter huang wrote:
thanks for the quick reply. I understand that gss_init_sec_context try to
erase the context which in this case
Jeffrey == Jeffrey Altman [EMAIL PROTECTED] writes:
Jeffrey peter huang wrote:
Can someone tell me how to fix this error? this error came
from curl using --negotiate option on a window platform using
MSLSA: as ccache (AD is the KDC in this case). the client is
Sam Hartman wrote:
Jeffrey == Jeffrey Altman [EMAIL PROTECTED] writes:
Jeffrey peter huang wrote:
Can someone tell me how to fix this error? this error came
from curl using --negotiate option on a window platform using
MSLSA: as ccache (AD is the KDC in this case).
Kevin == Kevin Coffman [EMAIL PROTECTED] writes:
Jeffrey == Jeffrey Altman [EMAIL PROTECTED] writes:
Jeffrey peter huang wrote:
Can someone tell me how to fix this error? this error came
from curl using --negotiate option on a window platform
using MSLSA: as
peter huang wrote:
Can someone tell me how to fix this error? this error came from curl using
--negotiate option on a window platform using MSLSA: as ccache (AD is
the KDC in this case). the client is windows XP using MIT 1.3.5 library.
BTW, I also experience the same error with kerberos
