[1408] in SIPB_Linux_Development
Re: problems with RedHat-Athena
daemon@ATHENA.MIT.EDU (Emil Sit)
Wed Aug 28 08:07:37 1996
To: Edwin Foo <efoo@MIT.EDU>
Cc: linux-dev@MIT.EDU
In-Reply-To: Your message of "Wed, 28 Aug 1996 01:58:14 EDT."
<199608280558.BAA01239@kabuf.mit.edu>
Date: Wed, 28 Aug 1996 08:07:00 EDT
From: Emil Sit <sit@MIT.EDU>
> 1) remote logins don't work (not allowed to log in here) unless
> the remote user is already logged on from console. ex: efoo
> cannot telnet to the machine unless he is already logged on
This is the correct behavior. The idea is that we don't want random
people to be able to login to your machine remotely. So, telnetd will
only allow login for users which are already in your /etc/passwd file.
You can allow arbitrary users to login by editing /etc/athena/rc.conf and
changing NOREMOTE to false and rebooting. [You don't actually have to
reboot; you can just "rm /etc/noremote", but you'll need to have that
variable set for it to work right after the next reboot.]
OTOH, if you want to only allow specific users, you can add them to
/etc/passwd directly. As root, run:
hesinfo <user> passwd >> /etc/passwd
That will append a line like:
efoo:*:10195:101:Edwin Foo,FooBunny,MIT LCS,32376,2258837:/mit/efoo:/bin/athena/tcsh
to your passwd file.
> I have executed said commands on my machine... cleared up some but not
> all of false login ghosts problems. Probably related to (1). I would
> really like to be able to log into my own machine, so help would be
> appreciated. So far I'm stumped as to why this is happening.
If those commands fix the utmp/wtmp problems, we probably need to update
the paths used in by telnetd. I personally think that /etc/utmp should
at least exist...
Emil
--
Emil Sit / Bronx Science '95, MIT '99 -- ESG, SIPB.
Email: <sit@mit.edu>, <esit@bxscience.edu> / Web: http://web.mit.edu/sit/www/
PGP fingerprint: A6 8F D0 69 3E DA BA 19 26 71 EC 1F 22 49 8F 58
"What has it gots in its slasheses? Curse the Gates!
We hates him forever!" <4t7tbg$e8n@csnews.cs.colorado.edu>
