[643] in Kerberos

home help back first fref pref prev next nref lref last post

bringing it up under SunOS 4.0

daemon@TELECOM.MIT.EDU (Ron Reisor)
Tue Jan 31 11:34:10 1989

From: Ron Reisor <ron@pyr1.acs.udel.edu>
To: kerberos@ATHENA.MIT.EDU


I've run into a number of problems trying to bring up Kerberos on SunOS4.0
on a Sun4 (sparc) architecture system.

In include/krb.h:
     The defines FD_ZERO, FD_SET, and FD_ISSET are already defined in the
SunOS 4.0 .h files, so I just changed the cpp lines so they would not
be included.  Likewise for the typedefs for uid_t and gid_t.

In util/imake.includes/config.Imakefile:
     define NEED_STRCASECMP and NEED_SETENV

In lib/krb/{klog,log}.c:
     These routines have a variable number of arguments, and they just
aren't portable unless you use the varargs routines.  It's easy to rewrite
these two routines to use varargs so I won't include the details.

In server/kerberos.c:
     Line 337 declares an int called client_host.  This should be declared
as 'struct in_addr' since that is what the routine inet_ntoa expects.  To
pass it to routines like krb_create_ticket use client_host.s_addr.  I'm
a little worried that this sort of problem might exsist in other peices of
Kerberos code.

There is another problem which I didn't really track down:
     If I define KRB_MASTER to be "core" and KRB_REALM to be "acs.udel.edu"
in the include/krb.h file, and I neglect to include the name core.acs.udel.edu
in the /etc/hosts file, then programs like kinit get segmentation violations.
This is clearly a silly test on my part, but it would be nice if the Kerberos
code handled this a little more elegantly.

And just so I don't sound like I'm complaining -- the code in general looks
quite good.  We are quite glad that Kerberos has been released

cheers,
Ron

home help back first fref pref prev next nref lref last post