It is uphemistically called Schecterware in honor of it's author - Michael Schechter. Before we continue to look at the login process in more detail, I need to explain one more requirement that was solved at this time by extending Shechterware. An external process makes certain that for every NIS account there is a matching NDS account. But this cannot create a properly encrypted password. This requires a copy of the cleartext password which is only availible during the users login process.
All user accounts are members in the container named students.students.
All administrative accounts are located in other containers. We have the abilty in this way to have an administrative account with the ability to change user passwords exclusively - without the ability to make any other changes to the system. We have the ability to leave this password management account somewhat exposed to potential reverse engineering of the binary, possible local packet capture, or other unspecified compromise because there is no sensitive private user data on the Netware server at this time. Netware is used for application storage. Personal data is hosted on the Samba server.