[11414] in Athena Bugs
[jweiss@MIT.EDU: Re: login program]
daemon@ATHENA.MIT.EDU (jweiss@MIT.EDU)
Mon Nov 22 23:08:19 1993
From: jweiss@MIT.EDU
To: bugs@MIT.EDU
Date: Mon, 22 Nov 93 23:08:10 EST
------- Forwarded Message
Received: from MIT.MIT.EDU by po6.MIT.EDU (5.61/4.7) id AA20361; Mon, 22 Nov 93 21:59:22 EST
Received: from TLA.MIT.EDU by MIT.EDU with SMTP
id AA10948; Mon, 22 Nov 93 21:59:03 EST
From: jweiss@MIT.EDU
Received: from localhost by tla.MIT.EDU (8.6.4/4.7+)
id VAA27284; Mon, 22 Nov 1993 21:58:57 -0500
Date: Mon, 22 Nov 1993 21:58:57 -0500
Message-Id: <199311230258.VAA27284@tla.MIT.EDU>
To: haynes@cats.ucsc.edu (Jim Haynes)
Cc: bugs@MIT.EDU, bug-dialup@MIT.EDU
In-Reply-To: [11404] in bugs
Subject: Re: login program
The test for existence of /etc/nlogin is rather late in the process.
I was working on a time sharing server (cf. dialup server) and had created
/etc/nologin, and noticed that users were trying to log in and that
their lockers kept getting attached and they kept getting edited into
the passwd file even tho they were not allowed to log in. I could have
prevented that by also creating noattach and nocreate; but it would make
more sense to have the test for nologin earlier in the process.
We have, in fact, seen such behavior on Athena's dialup servers (at
least the locker attaching, I don't recall whether they are added to
the passwd file. but I expect that they were.
Jonathon Weiss
jweiss@mit.edu
Athena Systems Support
------- End of Forwarded Message
