[4810] in Kerberos
Solaris 2.{34} rlogind
daemon@ATHENA.MIT.EDU (Michael Helm)
Wed Mar 15 15:05:15 1995
To: kerberos@MIT.EDU
Date: 15 Mar 1995 18:37:55 GMT
From: mike@fionn.lbl.gov (Michael Helm)
Reply-To: mike@fionn.lbl.gov (Michael Helm)
I've been having a lot of trouble getting a functional rlogin/rlogind
combination working on Solaris 2.3 or 2.4. Most of the trouble lies
in rlogind (rlogin to other OS hosts works, even if not quite up
to spec). It looks to me like the configuration script made
a fairly mixed up set of compiler variables (some bsd, some sys v
stuff), which results in a daemon that doesn't use the /dev/pty/#
devices but the ttyp* devices, & some other confusion. There
is also a communication problem between the daemon & the remote
login (more info on this on request). Looking at the source, &
experimenting with the compilation parameters doesn't get me too
far -- it doesn't look to me like this version of rlogind.c has
much in the way of working sys V-anything code in it. This
particular version really seems to be a bit of a tangle, anyway.
Very hard to follow all the ifdef combinations in it.
I've also looked into porting other rlogind to kerberos. I have
some old Solaris 2.2 source available, but I can't get that stuff
to compile at all. I've looked at the logdaemon (tcp wrappers) rlogind,
which is based on an older bsd 43 rlogind but seems to work well on
solaris 2.3 & 2.4. I've run into problems with kerberizing this, tho,
in that the login.krb5 program & logdaemon rlogind don't seem to
communicate properly. (This is something other than what happens
at execl log-program time, I think, but I've just started looking
at this problem.)
Does anyone have any advice or ideas about a way out of this maze?
Thanks,
==mwh
