I had no idea that telnetd could do this. This presents a problem though, doesn't it? If /bin/login does all the work, then how can telnetd find what name was ultimately given to the credentials cache file, or even if login succeed at all? Nico On Tue, Aug 15, 2000 at 11:16:18AM -0400, Jeffrey Altman wrote: > I'm not sure you understand what I am referring to. The user logs in > with telnetd and 10 hours later the user's credentials expire. The > user does not want to log in again to the remote host. The user gets > new credentials locally (and in the case of Win2000 the operating > system does this for you automatically) and wants the new credentials > forwarded to the host. There is no /bin/login or /bin/su process > being executed by telnetd. That already happened when the initial > credentials are received. > > What is required is for the telnetd process to update the user's > credentials cache after the user is already logged in. > > > > Jeffrey Altman * Sr.Software Designer > The Kermit Project * Columbia University > 612 West 115th St * New York, NY * 10025 * USA > http://www.kermit-project.org/ * kermit-support@kermit-project.org > --
