Complete.Org: Mailing Lists: Archives: discussion: April 2001:
[aclug-L] Shells

[aclug-L] Shells

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: discussion@xxxxxxxxx
Subject: [aclug-L] Shells
From: Steven Saner <ssaner@xxxxxxxxxxxxxxx>
Date: Fri, 6 Apr 2001 00:17:27 -0500
Reply-to: discussion@xxxxxxxxx

Everyone that reads linux-help knows that I am involved in an ISP
venture. I wanted to get some peoples input on the concept of shell
servers. One of the common questions that is asked about an ISP,
especially from people on a list such as this, is: do they offer shell

First of all, I understand the value of a shell based computing
environment. I am all over that. I wouldn't compute without it (or I
wouldn't want to anyway). But with Linux, and other assorted free Unix
like OS's, I don't need my ISP in order to have a shell based

So, my question is, why do people want their ISP to offer shells? What
do you want in the shell service? In other words, what would you use
the shell for, that you can't do yourself?

It is somewhat difficult to build an ISP model that scales well, is
secure, etc. and support shell access. Most of the security issues
that come up are "local user" issues, so if you support shells, you
have to keep on top of the updates more religiously. A shell gives a
customer the ability to do things that you might not want them doing,
such as running processes and the like that can be a denial of service
to other customers.

Any comments would be welcome.


-- This is the discussion@xxxxxxxxx list.  To unsubscribe,

[Prev in Thread] Current Thread [Next in Thread]