From d95b3ba8a5ee61a8ef974ef8ebb727e9abbfe83c Mon Sep 17 00:00:00 2001 From: John Johansen Date: Tue, 31 Jul 2018 06:35:20 +0000 Subject: [PATCH] Update About --- About.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/About.md b/About.md index 62b60b9..974dbc9 100644 --- a/About.md +++ b/About.md @@ -12,9 +12,9 @@ to system services and daemon's (dbus, gsettings, X, ...) allowing its policy enforcement integration beyond what isolation allows. Specifically AppArmor is a variant of [Domain Type Enforcement -(DTE)](http://citeseer.ist.psu.edu/viewdoc/summary?doi=10.1.1.37.1501) -which is itself a variant of [Type Enforcement -(TE)](https://en.wikipedia.org/wiki/Type_enforcement). While AppArmor +(DTE)](http://citeseer.ist.psu.edu/viewdoc/summary?doi=10.1.1.37.1501), + which a variant of [Type Enforcement +(TE)](https://en.wikipedia.org/wiki/Type_enforcement), crossed with a [capability system](???). While AppArmor is capable of providing a total system policy its policy is designed and focused around an application (domain) centric model allowing for easy targeting of specific applications or users. Because AppArmor