[123] in Athena Bugs
A bug with attached filesystems
daemon@ATHENA.MIT.EDU (John Carr)
Mon Apr 4 08:13:04 1988
To: bugs@ATHENA.MIT.EDU
Date: Mon, 04 Apr 88 07:12:13 EST
From: John Carr <jfc@ATHENA.MIT.EDU>
Program with which you had the problem:
Name of person who discovered the bug: John F. Carr
Their MIT phone number: 5-6185
Their MIT address: East Campus Goodale 110
Their Athena Login ID: jfc
Name of consultant reporting bug:
------------------------------------------------------------------------
A brief synopsis of the problem:
Workstation acts as if userid changed, or filesystem as if Kerberos
ticket lost; home directory accessible only by world permissions.
------------------------------------------------------------------------
Please describe the problem in detail:
[This has happened twice, on M66-080-5 and -8]
On a workstation which fails to deactivate (and so never detaches
attached filesystems) (can be identified by grey background, instead
of "hit any key...") I logged in. After being logged in for a while
(over one hour in one case, perhaps a half hour in the other) I was
unable to access my files. My permissions are set so that only I
can read my files (I think this is the Athena default). In every
way I could check, it was as if I were some other user trying to
access someone else's files.
For example: (when this happened with the "sgs" account)
sgs > cat space.mss
cat: read error: I/O error
sgs >
sgs > cat > d
d: Permission denied
sgs >
(permissions are:
drwxr-xr-x 10 sgs 1024 Apr 4 06:23 .
-rw------- 1 sgs 1829 Apr 1 13:39 space.mss
)
Something similar has happened before, in an older release of the operating
system (last fall's bug-filled release). When Kerberos failed on login, I
attached my filesystem before getting tickets. It then behaved the same way
it does now (except that now I can use my filesytem for some time before it
fails).
Both times, "who" revealed someone else logged in (not active, but a process
which didn't die on logout and was never killed because the workstation
never deactivated).
"kinit" does not fix the problem. "kinit" followed by detaching and
reattaching my filesystem does.
------------------------------------------------------------------------
Repeat by:
Find a workstation which will not deactivate (the screen will blank
after a few minutes, but the login window is still there [only hidden]).
Login and wait. I don't know how reproducible this is, but it has
happened twice in 4 days.
