Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!maverick.ksu.ksu.edu!kuhub.cc.ukans.edu!wuarchive!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!emory!utkcs2!ornl.gov!jnm
From: jnm@ornl.gov (Jamey Maze)
Newsgroups: comp.sys.mac.comm
Subject: Re: Telnet INTO a Mac ?
Message-ID: <1991Mar19.183131.516@cs.utk.edu>
Date: 19 Mar 91 18:31:31 GMT
References: <1991Mar14.011826.18836@marlin.jcu.edu.au> <18365@milton.u.washington.edu> 
 <1991Mar14.060604.19964@PacBell.COM> <1991Mar15.141509.1224@watserv1.waterloo.edu>
Sender: usenet@cs.utk.edu (USENET News Poster)
Organization: Martin Marietta Energy Systems
Lines: 17

In article <1991Mar15.141509.1224@watserv1.waterloo.edu> 
psych@watserv1.waterloo.edu (R. Crispin - Psychology) writes:
> A caution if you use NCSA Telnet to allow FTP to the MAC. YOU CANNOT 
> RESTRICT ACCESS IN ANY WAY. People could FTP to your MAC and GET or 
> DELETE or PUT anything, anywhere.  ...

This is the one feature that makes TCP/Connect II worth purchasing (IMHO). 
It allows you to define user accounts (like NCSA Telnet's ftppass 
program), but it also allows you to set a "restricted folder" for each 
account.  A user ftp'ing into an account with a restricted folder could 
operate on files/folders inside/below the restricted folder, but they can 
not back up the tree above the restricted folder...

Jamey Maze
Oak Ridge National Lab
Internet: jnm@ornl.gov     Bitnet: jnm@ornlstc
Phone: 615/574-6355        Fax: 615/576-2912