RE: Problems with ksu in krb5-1.4.1
Yes, this patch is indeed working, both on Solaris 8 and Solaris 10. A
> -----Original Message-----
> From: [email]email@example.com[/email]
> [mailto:firstname.lastname@example.org] On Behalf Of Heilke, Rainer
> Sent: Tuesday, June 21, 2005 8:43 AM
> To: Ken Raeburn
> Cc: Garrett Wollman; [email]email@example.com[/email]
> Subject: RE: Problems with ksu in krb5-1.4.1
> My colleague has been testing the patch you provided, and so
> far, things
> are looking good. I'll update when we have a definitive answer.
> Thanks again for all of your help.
> > -----Original Message-----
> > From: Ken Raeburn [mailto:raeburn@MIT.EDU]
> > Sent: Wednesday, June 15, 2005 5:03 PM
> > To: Heilke, Rainer
> > Cc: Garrett Wollman; [email]firstname.lastname@example.org[/email]
> > Subject: Re: Problems with ksu in krb5-1.4.1
> > On Jun 15, 2005, at 18:00, Heilke, Rainer wrote:[color=darkred]
> > > This is on Solaris 8.
> > >
> > > I've passed the patch on. Thanks.[/color]
> > That patch was for a thread support problem that I thought might've
> > been Garrett Wollman's problem.
> > This patch to src/lib/krb5/ccache/cc_file.c should fix your[/color]
> > It might also fix the problem he ran into, I'm not sure.
> > Please let me
> > know...
> > Ken
> > Index: cc_file.c
> > ===================================================================
> > RCS file: /cvs/krbdev/krb5/src/lib/krb5/ccache/cc_file.c,v
> > retrieving revision 5.45
> > diff -p -u -r5.45 cc_file.c
> > --- cc_file.c 13 Apr 2005 16:55:40 -0000 5.45
> > +++ cc_file.c 15 Jun 2005 22:58:03 -0000
> > @@ -1459,7 +1459,7 @@ static krb5_error_code dereference(krb5_
> > kerr = k5_mutex_lock(&krb5int_cc_file_mutex);
> > if (kerr)
> > return kerr;
> > - for (fccsp = &fccs; *fccsp == NULL; fccsp = &(*fccsp)->next)
> > + for (fccsp = &fccs; *fccsp != NULL; fccsp = &(*fccsp)->next)
> > if ((*fccsp)->data == data)
> > break;
> > assert(*fccsp != NULL);
> Kerberos mailing list [email]Kerberos@mit.edu[/email]
Kerberos mailing list [email]Kerberos@mit.edu[/email]