[874] in Moira
Registration Problems for Staff
daemon@ATHENA.MIT.EDU (mgood@MIT.EDU)
Wed Mar 22 09:12:16 1995
From: mgood@MIT.EDU
Date: Wed, 22 Mar 1995 09:12:08 -0500
To: dkk@MIT.EDU, moira-admin@MIT.EDU, moiradev@MIT.EDU
Cc: accounts@MIT.EDU
Hi!
I'd like to politely disagree with dkk about people being able to register
with existing listnames being a development problem.
While it is true that we could change Moira so it wouldn't allow this, we
could also fix it by changing all the MITS people who haven't registered
from status 4 (which only lets them register for a Kerberos principal) to
status 0 (which would let them register for a full account.
If they could register for a full account, then they wouldn't be able to
register as "gopher", for instance. It's just because they can only
register for a kerberos principal that this problem arises.
Since all staff are eligible for accounts anyway, it seems to me that the
easiest and most immediate way to fix this problem would be to change all
people currently at status 4 to status 0, and change the default for
incoming MITS from status 4 to status 0. This would also cut down on the
need for MITS people to call accounts to have their Athena account set up.
I don't know how much work this would be, but once it was done we wouldn't
have to worry about it again. I realise that Account Deactivation is a
priority now, but is there some way this can be put on someone's todo list
so that it'll get done in the next few months? We've only had one major
"incident" because of this problem, so it's not life or death... but it
could be ;-)
Respectfulyy Yours,
Matt