in my opinion, chroot is suitable for some of the OSS projects,
depending if it is needed or not. At the moment we are busy with
a lot of different projects, PUB400.COM is only one of them.
Maybe there should be some documentation project to clearly define
which kind of software (e.g. node.js python php etc) can make good
use of a chroot environment, and others which do not need this.
On a shared public system like PUB400 it is always a good idea to
separate users which is mainly done on object security, but some
OSS software depends on other methods - also they depend on the
knowledge of admin and user ;-)
PUB400.COM currently has 1300 users (with 30-40 new users a day),
so i am not sure what would be the impact to the system if
a full chroot environment would be added for each user automatically.
Any thoughts? Especially from Aaron - how about an OSS definition for
free sandbox systems, or are you going only on a commercial setup? ;-)
Am 11.08.2016 um 18:41 schrieb John Yeung <gallium.arsenide@xxxxxxxxx>:
(I don't fully understand chroot, but from what I can gather, it would
seem Litmis Spaces uses it while pub400.com doesn't.)