Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!apple!amdahl!shs From: shs@uts.amdahl.com (Steve Schoettler) Newsgroups: comp.sources.d Subject: Re: getty/login for callback Keywords: tip getty login Message-ID: <18yLb6a0ib1010aFV6Y@amdahl.uts.amdahl.com> Date: 12 Apr 89 20:38:06 GMT References: <180001@mechp10.UUCP> <13853@rpp386.Dallas.TX.US> <797@twwells.uucp> <14U6Pf88Sj1010WE=r6@amdahl.uts.amdahl.com> <623@peritek.UUCP> Reply-To: shs@amdahl.uts.amdahl.com (Steve Schoettler) Distribution: usa Organization: Amdahl Corporation, Sunnyvale CA Lines: 44 In article <623@peritek.UUCP> dig@peritek.UUCP (Dave Gotwisner) writes: >In article <14U6Pf88Sj1010WE=r6@amdahl.uts.amdahl.com>, shs@uts.amdahl.com (Steve Schoettler) writes: ># ># I wrote something like this by modifying the standard unix tip program. ># This allowed taking advantage of a standard text file format for storing phone ># numbers, baud rates, etc. This also allows operation under a variety of ># modems (hayes and ventel). ># The program was invoked with "ntip myname", where there was an entry for ># myname in /etc/remote. ># ># All you have to do is find the place where tip makes the connection, ># and fork a shell, setting stdin and stdout to the serial port. I ># think the command I actually used inside my exec was "rlogin localhost", ># because I had trouble creating a getty on the dial out line. You can ># set stdin and stdout of the shell with the dup() command. > >This works fine, if you are calling from a computer. If I have a terminal >at home (not a PC or workstation), I cannot run tip, I need some secure >program running on the UNIX box that I am calling to prevent illegal logins. >-- >------------------------------------------------------------------------------ >Dave Gotwisner UUCP: ...!unisoft!peritek!dig >Peritek Corporation ...!vsi1!peritek!dig >5550 Redwood Road >Oakland, CA 94619 Phone: 1-415-531-6500 Sorry, I guess I didn't explain it well enough. The goal is to save the user's personal phone bills. Here's what happens: user calls the computer. (can be from a terminal + modem or home computer + modem) user logs into the computer and runs ntip. then user logs off, hangs up, sets the modem on auto-answer, and the computer calls him up and forks a shell out the computer's serial port, which the user sees on his terminal, just as getty/login did when the user called the computer. Steve -- Steve Schoettler shs@uts.amdahl.com {sun,decwrl,pyramid,ames,uunet}!amdahl!shs Amdahl Corp., M/S 213, 1250 E. Arques Ave, Sunnyvale, CA 94088