Skip to content
This repository has been archived by the owner on Sep 16, 2021. It is now read-only.

sandboxing support #51

Closed
z3r0 opened this issue Aug 21, 2010 · 1 comment
Closed

sandboxing support #51

z3r0 opened this issue Aug 21, 2010 · 1 comment

Comments

@z3r0
Copy link

z3r0 commented Aug 21, 2010

Ability to function and integrate with sandbox technology (i.e FreeBSD Jails, FreeBSD Capsicum, etc...)

Essentially all the different components of the CMS should be able to function with each other in separate jails fir greater security. This would require that the CMS is designed in a modular way so that each piece can run independently with built in methods to communicate with the other pieces. For example the build system runs in one jail (or virtual machine), the database in another, the version control in another, the Symfony 2 framework in another, each domain/user in their own jail etc... but that they all function together.

This will require the cms to have a messaging system/protocol that works across jails without compromising security and running on minimal rights (non-admin) where possible.

@lsmith77
Copy link
Member

what does this require? could you elaborate a bit more?

This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants