mirrors/apparmor.d
1
0
Fork 0
mirror of https://github.com/roddhjav/apparmor.d.git synced 2024-12-25 06:27:49 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions 1
large set of apparmor rules for various distros
3040 commits 6 branches 0 tags 15 MiB
Go 76.5%
Shell 11.1%
Python 3.8%
Jinja 3.7%
HCL 2.5%
Other 2.4%
Find a file
Alexandre Pujol 33a66ef6a2
Some checks failed
Ubuntu / check (push) Has been cancelled
Details
Ubuntu / build (default, ubuntu-22.04) (push) Has been cancelled
Details
Ubuntu / build (default, ubuntu-24.04) (push) Has been cancelled
Details
Ubuntu / build (full-system-policy, ubuntu-22.04) (push) Has been cancelled
Details
Ubuntu / build (full-system-policy, ubuntu-24.04) (push) Has been cancelled
Details
Ubuntu / tests (push) Has been cancelled
Details
fix(integration): disable needrestart test due to upstream issue.
2024-11-21 20:22:52 +00:00
.github ci(github): split the final step in two. 2024-11-19 20:00:04 +00:00
apparmor.d fix(tunable): udbus can be any hex up to 16. 2024-11-21 20:02:16 +00:00
cmd Update to ABI4.0 for Arch Linux 2024-10-22 11:03:39 +00:00
debian build(debian): disable make check by default on pkg build. 2024-11-12 22:31:16 +00:00
dists tests: small fixes on builders scripts. 2024-10-16 23:58:48 +01:00
docs feat: profiles and integration tests improvments. 2024-11-19 19:04:27 +00:00
pkg build: ensure build task get the proper profile name. 2024-11-11 21:18:16 +00:00
share build: root -> share. 2024-10-11 22:31:06 +01:00
systemd feat(systemd): ensure dbus service are started after apparmor. 2024-10-06 20:19:09 +01:00
tests fix(integration): disable needrestart test due to upstream issue. 2024-11-21 20:22:52 +00:00
.gitignore chore: update gitignore. 2024-04-02 13:44:27 +01:00
.gitlab-ci.yml ci: update golangci-lint. 2024-10-19 22:57:08 +01:00
.golangci.yaml chore: improve linter settings & better packer VM build. 2023-09-29 20:55:24 +01:00
go.mod chore: all external go module have been removed. 2024-10-19 22:58:47 +01:00
go.sum chore: all external go module have been removed. 2024-10-19 22:58:47 +01:00
LICENSE Cleanup license file. 2021-04-01 14:47:01 +01:00
Makefile fix(ci): remove forced color from github action. 2024-11-19 21:35:39 +00:00
mkdocs.yml docs: add development workflow. 2024-10-02 01:08:06 +01:00
PKGBUILD build: ensure arch based build always works. 2023-07-08 22:59:54 +01:00
README.md doc: general update. 2024-08-30 20:38:30 +01:00
requirements.txt doc: add git-committers extension. 2024-09-25 22:33:32 +01:00

README.md

apparmor.d

Full set of AppArmor profiles

Warning

This project is still in its early development. Help is very welcome; see the documentation website including its development section.

Description

AppArmor.d is a set of over 1500 AppArmor profiles whose aim is to confine most Linux based applications and processes.

Purpose

  • Confine all root processes such as all systemd tools, bluetooth, dbus, polkit, NetworkManager, OpenVPN, GDM, rtkit, colord
  • Confine all Desktop environments
  • Confine all user services such as Pipewire, Gvfsd, dbus, xdg, xwayland
  • Confine some "special" user applications: web browsers, file managers, etc
  • Should not break a normal usage of the confined software

Goals

This project is originally based on the work from Morfikov and aims to extend it to more Linux distributions and desktop environments.

Concepts

One profile a day keeps the hacker away

There are over 50000 Linux packages and even more applications. It is simply not possible to write an AppArmor profile for all of them. Therefore, a question arises:

What to confine and why?

We take inspiration from the Android/ChromeOS Security Model, and we apply it to the Linux world. Modern Linux security distributions usually consider an immutable core base image with a carefully selected set of applications. Everything else should be sandboxed. Therefore, this project tries to confine all the core applications you will usually find in a Linux system: all systemd services, xwayland, network, Bluetooth, your desktop environment... Non-core user applications are out of scope as they should be sandboxed using a dedicated tool (minijail, bubblewrap, toolbox...).

This is fundamentally different from how AppArmor is usually used on Linux servers as it is common to only confine the applications that face the internet and/or the users.

Presentations

Building the largest set of AppArmor profiles:

Installation

Please see apparmor.pujol.io/install

Configuration

Please see apparmor.pujol.io/configuration

Usage

Please see apparmor.pujol.io/usage

Contribution

Feedbacks, contributors, pull requests are all very welcome. Please read apparmor.pujol.io/development for more details on the contribution process.

Development chat available on https://matrix.to/#/#apparmor.d:matrix.org

License

This Project was initially based on Mikhail Morfikov's apparmor profiles project and thus has the same license (GPL2).