source: trunk/athena/bin/lert/README @ 7779

Revision 7779, 2.2 KB checked in by cfields, 29 years ago (diff)
Initial revision
1development files for lert program
3lert is supposed to notify a user during login via zephyr or cat if the
4user belongs to a group (originally, users whose accounts are
5scheduled for deactivation).
7client/server needed (rather than simple world readable file) to
8protect privacy of those scheduled for deactivation (important since
9such accounts are often targets for crackers).
11client program uses kerberos to ask server if we need to notify.
12this assures server that client is who it says it is.
14server looks in database and returns string of characters, one
15character for each group.
17client then sends one message (zephyr or cat) for each character.
18files with messages are kept in well-known location, since I don't
19think either the text of the messages or the existence of the groups
20needs to be a secret.
22administrators of the lert system have lertload to add users with a
23letter group and lertdump to look at the db, lertstop to remove a
24category, and lertused to remove a user.
26idiot# files are test files I used to learn something about kerberos,
27the zwrite code from gms, and the improved zwrite code I'm using for
30idiot4 is a stand-alone version of the client/server without kerberos or
31networking.  It may turn out to be handy for showing the administrators
32just what lert will do...since it allows you to cheat and tell it which
33user name to use.
35krbreq.c and ticode.c are example code -- nonworking.
37lert.c is the client.
38  usage: lert [-z]
39lertsrv.c is the server.
40  usage: lert
41lertload.c is the db load.
42  usage:  lertload type < namefile
43lertdump.c is the db dump.
44  usage:  lertdump
45lertstop.c removes a category
46  usage:  lertstop type
47lertused.c removes a user
48  usage:  lertstop name
49lertsaid.c dumps the log db
50  usage: lertdump
52note: code here is neither well-commented nor particularly
53well-designed.  I think it all works, and given a bit more time,
54should comment it and package it better, but...
57  lertsrv actually sees every login in the place.  it might be
58interesting/useful sometimes to be able to track those (if there isn't
59anything else doing it).  you could add this pretty easily...
60  lertsrv also could count accesses, msgs, etc.  stats are so much fun.
Note: See TracBrowser for help on using the repository browser.