mirrors/apparmor.d
1
0
Fork 0
mirror of https://github.com/roddhjav/apparmor.d.git synced 2024-11-15 07:54:17 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

doc: cosmetic.

Browse Source
This commit is contained in:
Alexandre Pujol 2024-01-31 14:33:03 +00:00
parent 46641e6cc6
commit 70a8407bd7
No known key found for this signature in database
GPG Key ID: C5469996F0DF68EC
9 changed files with 1 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/concepts.md
View File

@ -2,8 +2,6 @@
title: Concepts title: Concepts
--- ---
# Concepts
*One profile a day keeps the hacker away* *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: 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:

2
docs/development/index.md
View File

@ -2,8 +2,6 @@
title: Development title: Development
--- ---
# Development
You want to contribute to `apparmor.d`, **thanks a lot for this.** Feedbacks, contributors, pull requests are all very welcome. You will find in this page all the useful information needed to contribute. You want to contribute to `apparmor.d`, **thanks a lot for this.** Feedbacks, contributors, pull requests are all very welcome. You will find in this page all the useful information needed to contribute.
??? info "How to contribute" ??? info "How to contribute"

2
docs/development/integration.md
View File

@ -2,8 +2,6 @@
title: Integration Tests title: Integration Tests
--- ---
# Integration Tests
!!! danger "Work in Progress" !!! danger "Work in Progress"
The purpose of integration testing in apparmor.d is to ensure the profiles are not going to break a program when used in the Linux distribution and desktop environment we support. The purpose of integration testing in apparmor.d is to ensure the profiles are not going to break a program when used in the Linux distribution and desktop environment we support.

2
docs/development/tests.md
View File

@ -2,8 +2,6 @@
title: Tests suite title: Tests suite
--- ---
# Tests suite
A full test suite to ensure compatibility across distributions and software is still a work in progress. Here is an overview of the current CI jobs: A full test suite to ensure compatibility across distributions and software is still a work in progress. Here is an overview of the current CI jobs:
**On Gitlab CI** **On Gitlab CI**

2
docs/full-system-policy.md
View File

@ -21,7 +21,7 @@ title: Full system policy
## Install ## Install
This feature is only enabled when the project is built with `make full`. [Early policy](https://gitlab.com/apparmor/apparmor/-/wikis/AppArmorInSystemd#early-policy-loads) load **must** also be enabled. This feature is only enabled when the project is built with `make full`. [Early policy](https://gitlab.com/apparmor/apparmor/-/wikis/AppArmorInSystemd#early-policy-loads) load **must** also be enabled. Once `apparmor.d` has been installed in FSP mode, it is required to reboot to apply the changes.
In `/etc/apparmor/parser.conf` ensure you have: In `/etc/apparmor/parser.conf` ensure you have:
``` ```

1
docs/index.md
View File

@ -2,7 +2,6 @@
title: AppArmor.d title: AppArmor.d
--- ---
# AppArmor.d
**Full set of AppArmor profiles** **Full set of AppArmor profiles**

2
docs/issues.md
View File

@ -2,8 +2,6 @@
title: Known issues title: Known issues
--- ---
# Known issues
Known bugs are tracked on the meta issue **[#75](https://github.com/roddhjav/apparmor.d/issues/74)**. Known bugs are tracked on the meta issue **[#75](https://github.com/roddhjav/apparmor.d/issues/74)**.
!!! info !!! info

2
docs/recovery.md
View File

@ -2,8 +2,6 @@
title: System Recovery title: System Recovery
--- ---
# System Recovery
Issue in some core profiles like the systemd suite, or the desktop environment can fully break your system. This should not happen a lot, but if it does here is the process to recover your system on Archlinux: Issue in some core profiles like the systemd suite, or the desktop environment can fully break your system. This should not happen a lot, but if it does here is the process to recover your system on Archlinux:
1. Boot from a Archlinux live USB 1. Boot from a Archlinux live USB

2
docs/report.md
View File

@ -2,8 +2,6 @@
title: Report AppArmor logs title: Report AppArmor logs
--- ---
# Report AppArmor logs
The **[aa-log](usage.md#apparmor-log)** tool reports all AppArmor `DENIED` and `ALLOWED`. It should be used to fix AppArmor related issues. The **[aa-log](usage.md#apparmor-log)** tool reports all AppArmor `DENIED` and `ALLOWED`. It should be used to fix AppArmor related issues.
While testing, if something get wrong, you need to put the profile in complain mode, so that you can investigate, and it does not block your program. While testing, if something get wrong, you need to put the profile in complain mode, so that you can investigate, and it does not block your program.