Message-Id: <199603022236.QAA28782@library.wustl.edu> Date: Sat, 2 Mar 1996 16:25:14 -0600 From: Alejandro Garza Gonzalez <mailto:agarza@CI.MTY.ITESM.MX> Subject: Re: Scripted Telnet Destinations To: Multiple recipients of list WEBCAT-L <mailto:WEBCAT-L@WUVMD.WUSTL.EDU>
On Sat, 2 Mar 1996, Selden Deemer wrote:> Alejandro Garza Gonzalez came closest to the mark, when he said:
>
> >This makes you non-standard for outside users, who won't know how to
> >properly configure their browsers and what external apps to add, but
> >it's the only way to do it that I know of.
>
> This is exactly the problem, but it's not limited to outside users.
> Even for local user populations of any significant size there is
> tremendous diversity, and providers typically have no control over
> what platform users may be running (typically Wintel or Macintosh,
> but also X folk, and Lynx users), what browsers they are using,
> what telnet software, or how they have their systems configured.
OK, thought of some other ways to do this:
1) Having a list of 'certified' machines, tell your telnetd on your telnet server machine to let certain users in automatically. Use TCPWrappers. Fully automatic login.
or
2) Make a login script on a passwordless account that lets connections from certified machines in, and tells others the service is not available. Semi-automatic, user must know what login to use, or could be told with a TCPwrapper banner (see next option)
or
3) Use TCPwrappers' telnetd to put up a banner that tells user what username and password to use, before he/she is prompted for them. Not automatic at all, but something the user can follow.
NOW, what do you want to be a 'certified' machine?
a) Machines that have looked up a web page on your http server -Have your cgi script talk to your telnet server and update its list of 'certified machines' (see option c below) b) All machines -Set up another telnet port on your telnet server that automatically lets users in, don't mess with the above options c) A selection of machines or subnets you control -Modify /etc/access.allow or /etc/access.deny to allow and/or block out certain addresses.
Hope I was clear enough.. and that this helps :)
Greetings
> Selden Deemer PHONE: 404-727-0271
> ATLANTA, GEORGIA EMAIL: mailto:libssd@emuvm1.cc.emory.edu
+-------------------------------------+------------------------------------+ | Ing. Alejandro Garza Gonzalez | E-MAIL: mailto:agarza@campus.mty.itesm.mx |
| ITESM University, Monterrey, Mexico | "Ok bye!" // Solo |
+- http://www-cib.mty.itesm.mx/ ------+-------------------------\X/-Amiga!-+