89caae2932
Here is a some example for avoiding a confusion. It asssumes a logged host domain is "spec.co.jp". All example is longer than UT_HOSTNAMELEN value. 1) turbo.tama.spec.co.jp: 192.19.0.2 -> trubo.tama 2) turbo.tama.foo.co.jp : 192.19.0.2 -> 192.19.0.2 3) specgw.spec.co.jp : 202.32.13.1 -> specgw Submitted by: Atsushi Murai <amurai@spec.co.jp> |
||
---|---|---|
.. | ||
klogin.c | ||
login_access.c | ||
login_fbtab.c | ||
login.1 | ||
login.access.5 | ||
login.c | ||
Makefile | ||
pathnames.h | ||
README |
This login has additional functionalities. They are all based on (part of) Wietse Venema's logdaemon package. The following defines can be used: 1) LOGIN_ACCESS to allow access control on a per tty/user combination 2) SKEY to allow the use of s/key one time passwords 3) LOGALL to log all logins -Guido This login has some of Berkeley's paranoid/broken (depending on your point of view) Kerberos code conditionalized out, so that by default it works like klogin does at MIT-LCS. You can define KLOGIN_PARANOID to re-enable this code. This define also controls whether a warning message is printed when logging into a system with no krb.conf file, which usually means that Kerberos is not configured. -GAWollman