[comp.protocols.kerberos] Installing Kerberos on Sun Sparc

he7@jnmsun.ctd.ornl.gov (Matt Hecht) (06/27/91)

	I'm having a slight problem installing Kerberos on a Sun 
SparcStation, and I was wondering if someone could help.  I'm having
trouble getting the ksu and login.krb applications to compile.  The
problem seems to be the setenv routine, which isn't in our C library.  
I've looked through the last few years of mail and seen that this
is a problem, but I didn't see a fix.  If anyone has run into this 
problem, could you help me out?  I think all that is needed is the
setenv routine.  Any comments or suggestions could be e-mailed 
to me (mhecht@cs.utk.edu), or posted to the newsgroup.  Any help
would be greatly appreciated.

--
Matt Hecht                      |  mhecht@cs.utk.edu (Internet)
Dept. of Computer Science       |
University of Tennessee         |  summer intern, ORNL, Oak Ridge, TN

seclark@iscnvx.uucp (Steve Clark) (06/29/91)

> From:  Matt Hecht  (mhecht@cs.utk.edu)
>
>   	I'm having a slight problem installing Kerberos on a Sun 
> SparcStation, and I was wondering if someone could help.  I'm having
> trouble getting the ksu and login.krb applications to compile.  The
> problem seems to be the setenv routine, which isn't in our C library.  
> I've looked through the last few years of mail and seen that this
> is a problem, but I didn't see a fix.  If anyone has run into this 
> problem, could you help me out?  I think all that is needed is the
> setenv routine.  Any comments or suggestions could be e-mailed 
> to me (mhecht@cs.utk.edu), or posted to the newsgroup.  Any help
> would be greatly appreciated.


Did you  have    #define  NEED_SETENV   in your  config.Imakefile?

----------------------------------------------------------------------

While on the subject, how clean is Kerberos level 4, patchlevel 9, 
supposed to  compile  for  Sun SPARCstations under SunOS 4.1.1  and for
DecStation 2100/3100's under Ultrix 4.0 rev 179 (I know Ultrix comes with 
Kerberos but I want to try MIT's version)? I get through the DES verification 
ok,  but there are a number of warning messages for the Sun such as:


"main.c", line 84: warning: illegal pointer combination
"cmd_tbl.lex.c", line 114: warning: illegal combination of pointer and integer,
op =
"listen.c", line 50: warning: illegal pointer combination
"read_password.c", line 188: warning: illegal pointer combination
"kadm_cli_wrap.c", line 429: warning: illegal pointer combination
"kdb_init.c", line 79: warning: illegal combination of pointer and integer, op =
"rcp.c", line 533: warning: illegal pointer combination
"rcp.c", line 534: warning: illegal pointer combination
"login.c", line 736: warning: illegal pointer combination
key_sched.c(150): warning: possible pointer alignment problem
des.c(244): warning: possible pointer alignment problem
des.c(246): warning: possible pointer alignment problem
des.c(249): warning: possible pointer alignment problem
des.c(251): warning: possible pointer alignment problem

cbc_encrypt.c(63): warning: possible pointer alignment problem
cbc_encrypt.c(64): warning: possible pointer alignment problem
cbc_encrypt.c(65): warning: possible pointer alignment problem

pcbc_encrypt.c(78): warning: possible pointer alignment problem
pcbc_encrypt.c(79): warning: possible pointer alignment problem
pcbc_encrypt.c(80): warning: possible pointer alignment problem

cksum.c(61): warning: possible pointer alignment problem
cksum.c(62): warning: possible pointer alignment problem
cksum.c(63): warning: possible pointer alignment problem

random_key.c(57): warning: possible pointer alignment problem
read_password.c(188): warning: illegal pointer combination
string_to_key.c(122): warning: possible pointer alignment problem
string_to_key.c(123): warning: possible pointer alignment problem

pkt_cipher.c(39): warning: possible pointer alignment problem

send_to_kdc.c(124): warning: possible pointer alignment problem
send_to_kdc.c(159): warning: possible pointer alignment problem
send_to_kdc.c(174): warning: possible pointer alignment problem

setenv.c(58): warning: possible pointer alignment problem
setenv.c(65): warning: possible pointer alignment problem

krb_cache.c(62): warning: i unused in function kerb_cache_get_principal
krb_cache.c(98): warning: found unused in function kerb_cache_put_principal
krb_cache.c(138): warning: i unused in function kerb_cache_get_dba
krb_cache.c(172): warning: found unused in function kerb_cache_put_dba

krb_kdb_utils.c(104): warning: possible pointer alignment problem

kadm_cli_wrap.c(124): warning: possible pointer alignment problem
kadm_cli_wrap.c(429): warning: illegal pointer combination

acl_files.c(269): warning: possible pointer alignment problem
acl_files.c(272): warning: possible pointer alignment problem
acl_files.c(314): warning: possible pointer alignment problem

----------------------------------------------------------------------

Similar, fewer, warnings for DecStation 2100,  but including:

error_table.c,  line 219: unknown directive == "#"
ct.c, line 111: unknown directive == "#"
kadm_cli_wrap.c, Warning (502) struc/union iovec never defined
kuserok.c, Warning (199) struc/union iovec never defined

----------------------------------------------------------------------

Steve Clark
Lockheed Misssiles & Space
seclark@iscnvx.lmsc.lockheed.com