Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mandatory access control #17

Open
jacksingleton opened this issue Nov 4, 2015 · 0 comments
Open

mandatory access control #17

jacksingleton opened this issue Nov 4, 2015 · 0 comments

Comments

@jacksingleton
Copy link
Collaborator

Two systems for MAC are apparmor and selinux. A third option is grsec rbac, but since it's unclear at this point whether sandstorm will even run on a grsec patched kernel (and even if it does relying on a grsec hardened kernel limits hosting options) lets focus on the first two at least for now.

I'm leaning towards apparmor for the following reasons:

  • It's much better supported in the Debian world
  • It's less work to understand, set up, and maintain
  • Even though we cant write a profile for Sandstorm itself, I don't think we'd get much benefit if we could [1]

So lets install/configure profiles for other important processes attached to the network.

[1]
The big advantage of selinux for us is that we might be able to write a selinux profile for sandstorm, but we cannot with apparmor because apparmor is file path based and sandstorm needs to be able to use 'mount' which can bypass any file path based restrictions.
BUT, sandstorm is the process that will be directly managing all of our users data... so confining with selinux will not limit any of that access if sandstorm itself is compromised. The only potential gain is that an attacker that compromises sandstorm might not be able to install a rootkit or otherwise mess with the server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant