Xref: utzoo comp.sources.d:2534 comp.sources.wanted:4653 comp.unix.questions:8450 comp.dcom.modems:2137 Path: utzoo!utgpu!attcan!uunet!mcvax!eurtrx!euraiv1!evas From: evas@euraiv1.UUCP (Eelco van Asperen) Newsgroups: comp.sources.d,comp.sources.wanted,comp.unix.questions,comp.dcom.modems Subject: Re: call back Message-ID: <723@euraiv1.UUCP> Date: 24 Jul 88 02:42:13 GMT References: <3208@edm.UUCP> Organization: Erasmus University EF/AIV,Rotterdam,Netherlands Lines: 32 in article <3208@edm.UUCP>, steve@edm.UUCP (Stephen Samuel) says: > 1) if you have the 'ct' command, you can use it to dial out and start > up a gety task, you would then need a command like; This is what I *intended* to mention in my previous posting; unforunately, my brain was disconnected from my fingers for a few seconds and I typed 'cu (call Unix)'. Oops. > One serious problem with the shell script is that it leaves your > system vulnerable to someone who manages to dial in between your > hanging up and the system dialing out (you'd have a shell running > at that point). If you invoke the standard getty from a shell that checks for a lock- file, you could dial-in, give the command to call back, which creates the lock, and logout. After the logout, the getty-shell notices the lock and starts to dial the number you requested. When a connection has been established, it forks off a getty to enable you to login. If this getty terminates, ie. you have logged out, it removes the lockfile, terminates the connection and restarts a getty to enable future logins. By taking the tty- and locking-routines from C-kermit, it should not be too hard to produce such a program. If I feel like it, I might even give it a go someday. -- Eelco van Asperen. uucp: evas@eurtrx / mcvax!eurtrx!evas #include earn/bitnet: asperen@hroeur5 #include "We'ld like to know a little bit about you for our files" - Mrs.Robinson, Simon & Garfunkel