Shell host

[fmadvocate at gmail.com (Frank Mileto)]

I would start by using some jailed environment. Maybe, OpenVZ,
Linux-VServer, or a *BSD jail.  I'm pretty sure chroot can be circumvented.


Frank Mileto

2008/12/15 xgermx <xgermx at gmail.com>

> Stop me if you feel like this is thread-jacking but, what if you are
> hosting shells for people you don't know?
> How do you secure your box and each account? (This is completely
> hypothetical. of course)
>
>
> On Mon, Dec 15, 2008 at 2:13 PM, Jonathan Moore <supermegatron at gmail.com>wrote:
>
> > 2008/12/15 xgermx <xgermx at gmail.com>:
> > > So everyone seems to think that DIY is best. What if you're hosting
> > shells
> > > for not only yourself, but others as well?
> > > Is hosting yourself still the best option?
> >
> > For simple shell accounts, sure.  If you're only going to be giving
> > access to friends / family then absolutely sure.  The next best thing
> > in my opinion would be to rent a dedicated server or colo and manage
> > the server yourself.
> >
> > -Jon
> > _______________________________________________
> > Pauldotcom mailing list
> > Pauldotcom at mail.pauldotcom.com
> > http://mail.pauldotcom.com/cgi-bin/mailman/listinfo/pauldotcom
> > Main Web Site: http://pauldotcom.com
>
>
> _______________________________________________
> Pauldotcom mailing list
> Pauldotcom at mail.pauldotcom.com
> http://mail.pauldotcom.com/cgi-bin/mailman/listinfo/pauldotcom
> Main Web Site: http://pauldotcom.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.pauldotcom.com/pipermail/pauldotcom/attachments/20081215/01d34d9a/attachment.htm