Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version VT1.00C 11/1/84; site vortex.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!ucbvax!decvax!bellcore!vortex!lauren
From: lauren@vortex.UUCP (Lauren Weinstein)
Newsgroups: net.micro.pc
Subject: Re: IBM Bulletin Board Software
Message-ID: <807@vortex.UUCP>
Date: Sun, 22-Sep-85 13:54:36 EDT
Article-I.D.: vortex.807
Posted: Sun Sep 22 13:54:36 1985
Date-Received: Tue, 24-Sep-85 03:20:17 EDT
References: <206@graffiti.UUCP>
Organization: Vortex Technology, Los Angeles
Lines: 19

It's actually trivial to set up "restricted shells" within UULINK.  Since 
every remote login user can be directed (if desired) to any desired program
(including COMMAND.COM, which is the general case) people are free to set
up whatever they want for remote users.  One UULINK user threw together a 
very simple "restricted shell" and sent it to me (it's only a couple of
screens worth of code).  I decided not to try include such programs in the
current package itself since different persons would have different ideas 
of the sorts of restrictions, and levels of restriction checking and other
"shell" features, that they really wanted for remote access users.
If I can find a general purpose "restricted shell" that isn't too large
I may decide to include it in the package.  However, in any case, it is very 
simple right now to set up individual UULINK logins to run specific
programs rather than COMMAND.COM, and (as the UULINK user I mentioned 
above demonstrated) programs for more elaborate restrictions on what 
can be remotely run (e.g. "restricted shells") are very simple to
write and drop directly into the existing UULINK remote access 
facilities if desired.

--Lauren--