[163] in testers
Re: 6.3B: activate/attach complaints
daemon@ATHENA.MIT.EDU (daemon@ATHENA.MIT.EDU)
Sun Jul 23 22:02:57 1989
Date: Sun, 23 Jul 89 22:02:38 EDT
From: Theodore Ts'o <tytso@ATHENA.MIT.EDU>
To: Ken Raeburn <raeburn@ATHENA.MIT.EDU>
Cc: Ken Raeburn <raeburn@ATHENA.MIT.EDU>, testers@ATHENA.MIT.EDU
In-Reply-To: Ken Raeburn's message of Sun, 23 Jul 89 17:11:16 -0400,
Reply-To: tytso@ATHENA.MIT.EDU
Date: Sun, 23 Jul 89 17:11:16 -0400
From: Ken Raeburn <raeburn@ATHENA.MIT.EDU>
How could this be done in a way that wouldn't have to be changed from
release to release? The only ways I can think of would key off such
things as the mount point. Perhaps something using the mount point in
the hesiod information, ignoring one requested by the user? This
seems questionable to me....
Well, since private workstation owners have to manually update their
workstation anyway, you could always ask them to update their exception
list when they take manually, assuming they really want to run in
paranoid mode. Or, they could put in something like this, which should
mostly work, as long as packnames stay roughly the same:
setuid {-}:^bldg.*-.....-[0-9][0-9].
- Ted
