summaryrefslogtreecommitdiff
path: root/example/apparmor
AgeCommit message (Collapse)AuthorFiles
2024-10-16[docs/bugfix] Fix access to /dev and /tmp in AppArmor profile (#3444)Libravatar Sqx. Flann van der Eik1
2024-09-28[chore] Update apparmor example file (#3368)Libravatar tobi1
2024-02-24[docs/bugfix] Allow access to TMP directories in example AppArmor config (#2683)Libravatar tux931
* Remove trailing whitespace from example config * Update and extend example AppArmor profile
2023-06-04[bugfix/docs] AppArmor profile for SQLite (#1864)Libravatar Daenney1
Our default configuration places the SQLite DB in /gotosocial/, but the AppArmor profile doesn't allow us to write there. Instead of making the whole directory writable, add a writable area in /gotosocial/db/ instead and advise in the docs to move the DB there.
2022-11-30[docs] Add AppArmor profile for Debian and Ubuntu installations (#1183)Libravatar kernelmethod1
* Enable the 'admonitions' Markdown extension for Mkdocs. The admonitions extension to Python-Markdown allows you to include rST-style "admonitions" to Markdown documents, for instance, !!! note Here's an important note to keep in mind! In general, the current documentation uses bold text to try to achieve the same effect, which is a bit harder to notice and makes it difficult to differentiate between "here's something useful to know" versus "here there be dragons". * Add AppArmor profile and documentation for LSM-related sandboxing This commit adds an AppArmor profile for gotosocial in examples/apparmor/gotosocial. This will (hopefully) serve as a helpful security mitigation for people are planning on deploying GTS on a Debian-family Linux distribution. I've also updates the documentation to include some information about deploying GTS with either AppArmor or SELinux (moving the documentation for the former out of the "binary installation guide" docs).