[423] in Moira
moira permission to access SIS
daemon@ATHENA.MIT.EDU (Mark Rosenstein)
Mon Jun 29 18:37:13 1992
Date: Mon, 29 Jun 92 18:36:45 -0400
From: Mark Rosenstein <mar@MIT.EDU>
To: accounts@MIT.EDU, sis@MIT.EDU, moiradev@MIT.EDU
I'm not sure who will deal with tracking down SIS access problems, but
want to make sure that all of you know what is involved.
A user must:
* Have registered for their extra password at least 14 days
previously. If you examine the user account with moira, it will
either say: "No secure password set." or something like "Secure
password set on Jun 5 13:48:04 1992." If you modify a user account
with moira you can set this field back to not having a password, or
set it to having set a password right now.
* Have their account info signed. If you examine the user account
with moira, it will say either: "Signed: Yes", "Signed: No", or
"Signed: Bad" indicating that it is signed, it is not signed, or there
is an invalid signature. Whenever you modify an account with moira,
it will generate a new signature by the user running the client. We
will periodically do bulk signings (with various sanity checks) for
people who have registered.
We will not sign accounts whose MIT ID number is still encrypted. So
this is a possible cause of failures.
-Mark
