Subject: Pine and E-Mail account only

From: Jamie Wyatt <[email-masked]>
Date: Fri, 21 Jan 1994 08:42:46 -0500 (EST)

Are there any options in the .prinerc file or compile flags that can be 
set to make pine/pico appropriate for a captive e-mail account only? 
Basically I want to keep e-mail only users from being able to leave their 
home directory via the ^T to files type stuff.
Even though I use the restricted shell pine/pico still allows them to 
move about.

Just thought I would ask before I go start digging through the 
code.

Thanks
Jamie

------------------------------------------------------
Jamie Wyatt
Network and Systems Administrator
Dept. of Computer Science, Brock University
St. Catharines, Ontario, Canada, L2S 3A1
[email-masked]

---

From: [email-masked] (Kate M Jeary)
Date: Fri, 21 Jan 1994 14:54:57 +0000 (GMT)

Which particular restricted shell are you talking about? We operate with
a restricted shell developed in perl locally. We have also restricted the
use of certain options within Pine (such as the alternative-editor-command
and the personal print command) on a system-wide basis since these are the
major holes through which our users attempt to escape. 

We run Pine 3.89 under SunOs 4.1.3 (unix) on two 10/51s with a telnet
interface on one machine, and imap/pop access on the other.

If this is of interest to you, then surely you are welcome to the sum of
our shared experience...  

Jamie Wyatt

-- 
Internet: [email-masked]       University Computing Service,
JANET:    [email-masked]       Computer Laboratory, Pembroke St,
Phone:    +44 223 334447                Cambridge CB2 3QG, England.

---

From: Billy Barron <[email-masked]>
Date: Fri, 21 Jan 1994 08:54:40 -0600

>Even though I use the restricted shell pine/pico still allows them to 
What we do here is to log them into a chroot environment that only
has absolutely what that user needs to operate.  Everything except
their directory, tmp, and /var/spool is mounted read-only.  If they
do look around, all they won't see any other user's files anyway.
We run from a menu instead of a shell however.

-- 
Billy Barron,  Network Services Manager, Univ of Texas at Dallas
[email-masked]