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

Add Apparmor #101

Open
ghost opened this issue Jan 15, 2014 · 4 comments
Open

Add Apparmor #101

ghost opened this issue Jan 15, 2014 · 4 comments

Comments

@ghost
Copy link

ghost commented Jan 15, 2014

https://wiki.debian.org/AppArmor/HowTo

@ghost ghost self-assigned this Feb 1, 2014
@ghost
Copy link
Author

ghost commented Feb 1, 2014

from tails blog:
A critical problem with stacked filesystems, such as aufs, must be fixed at upstream level before we can use AppArmor in Tails. It should be fixed in AppArmor 3.0, which is scheduled for 2013 Q3.

It can be workaround'd if https://bugs.launchpad.net/apparmor/+bug/888077 is fixed (a month or two of dev time, we're told), or by adding "Kernel based alias support" (being discussed privately, stay tuned).

https://bugs.launchpad.net/ubuntu/+source/casper/+bug/131976

@boyska
Copy link
Member

boyska commented Feb 7, 2014

I propose to defer this to the next version (the one after 0.2)

@ghost ghost modified the milestone: v0.2 Feb 7, 2014
@ghost
Copy link
Author

ghost commented Feb 7, 2014

I agree. Removed

@intrigeri
Copy link

FYI the limitations quoted above are not that hard to workaround: https://tails.boum.org/contribute/design/application_isolation/. See also Tails bugfix/8007-AppArmor-hardening branch for more recent (still not ready nor merged) progress on this front -- especially the design doc should help understand what's going on.

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

No branches or pull requests

2 participants