The continuwuity service files restrict read/write paths but the configuration file can have arbitrary database paths #952
Labels
No labels
Bug
Cherry-picking
Database
Dependencies
Dependencies/Renovate
Difficulty
Easy
Difficulty
Hard
Difficulty
Medium
Documentation
Enhancement
Good first issue
Help wanted
Inherited
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Core
Matrix/Federation
Matrix/MSC
Matrix/Media
Meta
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
To-Merge
Wont fix
old/ci/cd
old/rust
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: continuwuation/continuwuity#952
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
conduwuit-example.toml
comes with an emptydatabase_path
(marked "YOU NEED TO EDIT THIS"). However, theconduwuit.service
files include flags that restrict which directories continuwuity can access, so the only value which works when running continuwuity as a systemd service is/var/lib/conduwuit
(which notably is not the example value provided in the configuration).Hmm, the service files should probably set it in an env var (
CONTINUWUITY_DATABASE_PATH
), and then the docs updated to reflect that