Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/mk-fg/apparmor-profiles

My local AppArmor profiles for apps that can use those
https://github.com/mk-fg/apparmor-profiles

apparmor-profile desktop linux lsm sandboxing security

Last synced: about 1 month ago
JSON representation

My local AppArmor profiles for apps that can use those

Host: GitHub
URL: https://github.com/mk-fg/apparmor-profiles
Owner: mk-fg
Created: 2012-02-05T07:00:16.000Z (over 12 years ago)
Default Branch: master
Last Pushed: 2024-02-03T15:51:05.000Z (7 months ago)
Last Synced: 2024-02-14T21:14:52.985Z (7 months ago)
Topics: apparmor-profile, desktop, linux, lsm, sandboxing, security
Language: Python
Homepage:
Size: 227 KB
Stars: 66
Watchers: 8
Forks: 17
Open Issues: 0
Metadata Files:
- Readme: README.rst

Awesome Lists containing this project

README

apparmor-profiles
=================

AppArmor profiles I use for binary or potentially complex/dangerous/exposed apps
like browsers, random electron and wine stuff, proprietary things, etc.

Repository URLs:

- https://github.com/mk-fg/apparmor-profiles
- https://codeberg.org/mk-fg/apparmor-profiles
- https://fraggod.net/code/git/apparmor-profiles

On the desktop, even confined to user's uid, such apps still get unwanted access
to a lot of things in $HOME and can read a lot of poorly-secured files on the system
(like /etc/passwd or some non-chmodded config), which is obviously undesirable,
and what AppArmor can help to fix.

Some profiles and abstractions are reused from upstreams like ubuntu, suse and
various misc other repos, but often found them too lax or bloated for specific
system (currently Arch Linux), allowing stuff like ``@{HOME}/** r``, so prefer to
use them just for reference, copying only obvious and safe access lines from there,
getting (or confirming) the rest from audit logs.

Main doc on rule syntax:
https://gitlab.com/apparmor/apparmor/wikis/AppArmor_Core_Policy_Reference

I use apparmor_init_ script (under "scripts" dir) to load these profiles with
some caching and "--override-policy-abi" option to avoid needing boilerplate
for it in every file - they are intended to always work together anyway.

.. _apparmor_init: scripts/apparmor_init

Important note
--------------

This is more of a "my configuration" repository, and profiles here are mostly
written in an ad-hoc fashion for my system, not to be generic fit for any linux
(or even app usage scenario) out there.

Plus I'm no security expert, so can - and do - miss some things, only making
sure that the most obvious bad things can't happen (or will trigger a warning),
not trying to build super-secure system or anything, thinking of it more like
basic hygeine than hardening against a dedicated attacker.

Therefore it might be wise to only use these profiles for reference
(e.g. to get the general idea where app needs access), and not as a drop-in config.

Some paths in profiles like @{HOME\_GIT} and @{SYS\_GIT} are specific to my
systems (configuration git repos), and can/should be removed or updated to some
other local paths.