[244] in Kerberos-V5-bugs
Typo in krshd.c
daemon@ATHENA.MIT.EDU (Asokan)
Fri Nov 6 10:04:48 1992
From: Asokan <nasokan@yoho.uwaterloo.ca>
To: krb5-bugs@Athena.MIT.EDU
Date: Fri, 6 Nov 1992 10:02:59 -0500
Even in K4, krshd defined "environ" as a global and not
an extern. This works on most systems that do block common
initialization. But lately, some have begun to do the right
thing (like DEC Ultrix 4.2 - Mips). I am sending in this
patch because even K5 seems to have the same oversight.
On machines that don't do block common initialization this
bug has the effect of not setting the environment correctly.
e.g: krsh <machine> printenv HOME would, for instance, return
"/".
Asokan
-----
***************
*** 318,324 ****
#endif /* CRAY */
#endif /* KERBEROS */
! char **environ;
char ttyn[12]; /* Line string for wtmp entries */
#if defined (alliant) /* Alliant compiler complains of too many
--- 318,324 ----
#endif /* CRAY */
#endif /* KERBEROS */
! extern char **environ;
char ttyn[12]; /* Line string for wtmp entries */
#if defined (alliant) /* Alliant compiler complains of too many
