[OpenAFS] Kerberos 5, AFS, and no krb524d

Neulinger, Nathan nneul@umr.edu
Fri, 6 Jun 2003 15:09:32 -0500


Then you have a "big project" maintaining compatability with lots of
kerb distributions, instead of a small project doing so.... Latter is
much easier to maintain I believe.

I think that's the end goal, but getting there will be a while. We
currently don't have any dependency or integration of krb5 at compile
time into the openafs build. Maybe we should, not clear.

-- Nathan

------------------------------------------------------------
Nathan Neulinger                       EMail:  nneul@umr.edu
University of Missouri - Rolla         Phone: (573) 341-4841
Computing Services                       Fax: (573) 341-4216


> -----Original Message-----
> From: Rodney M Dyer [mailto:rmdyer@uncc.edu]=20
> Sent: Friday, June 06, 2003 3:07 PM
> To: openafs-info@openafs.org
> Subject: Re: [OpenAFS] Kerberos 5, AFS, and no krb524d
>=20
>=20
> What would please me more is getting rid of this "aklog" business=20
> altogether and just adding the functionality right into=20
> "klog" with a "-v5"=20
> option.
>=20
> IS THAT TOO MUCH TO ASK????????
>=20
> Rodney
>=20
> Rodney M. Dyer
> Windows Systems Programmer
> Mosaic Computing Group
> William States Lee College of Engineering
> University of North Carolina at Charlotte
> Email rmdyer@uncc.edu
> Phone (704)687-3518
> Help Desk Line (704)687-3150
> FAX (704)687-2352
> Office  267 Smith Building
>=20
>=20
> At 03:58 PM 6/6/2003 -0400, you wrote:
> > >Actually, what I think we really need is for=20
> grand.central.org to have a
> > >cvs repository that can be a one-stop source for aklog and=20
> some of these
> > >other addons. If they were all in one place, we could make=20
> some progress
> > >toward standardizing.
> >
> >Well, the afs-krb5 migration _is_ on grand.central.org, but=20
> I understand
> >why Derrick doesn't want to be in the aklog business.
> >
> >aklog ends up being a real pain in the ass piece of=20
> software.  It's tied
> >to both your Kerberos implementation _and_ your AFS=20
> implementation.  Just
> >compiling it can be a challenge.
> >
> >--Ken
> >_______________________________________________
> >OpenAFS-info mailing list
> >OpenAFS-info@openafs.org
> >https://lists.openafs.org/mailman/listinfo/openafs-info
>=20
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
>=20