[GH-ISSUE #3809] Relationship between disable-mnt and disable-write.inc #2405

New issue

Closed

opened 2026-05-05 09:05:01 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 09:05:01 -06:00

Owner

Originally created by @ghost on GitHub (Dec 11, 2020).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3809

I am wondering if I understand the difference/relationship between disable-mnt and (including) disable-write.inc correctly. The former blacklists /media, /mnt, /run/media and /run/mount access, while the latter makes those exact same directories read-only. Shouldn't it make sense to ONLY include disable-write.inc in profiles that DO NOT have disable-mnt?

If so, we might have to look at a few profiles that mix them up non-sensically, at least for me:

BAD:
- dbus-send.profile
- notify-send.profile
- qrencode.profile
GOOD
- eo-common.profile

Originally created by @ghost on GitHub (Dec 11, 2020). Original GitHub issue: https://github.com/netblue30/firejail/issues/3809 I am wondering if I understand the difference/relationship between `disable-mnt` and (including) `disable-write.inc` correctly. The former blacklists /media, /mnt, /run/media and /run/mount access, while the latter makes those exact same directories read-only. Shouldn't it make sense to ONLY include `disable-write.inc` in profiles that DO NOT have `disable-mnt`? If so, we might have to look at a few profiles that mix them up non-sensically, at least for me: - BAD: - dbus-send.profile - notify-send.profile - qrencode.profile - GOOD - eo-common.profile

gitea-mirror

2026-05-05 09:05:01 -06:00

closed this issue
added the
question_old
label

gitea-mirror commented

2026-05-05 09:05:05 -06:00

Author

Owner

@rusty-snake commented on GitHub (Dec 11, 2020):

I am wondering if I understand the difference/relationship between disable-mnt and (including) disable-write.inc correctly. The former blacklists /media, /mnt, /run/media and /run/mount access, while the latter makes those exact same directories read-only.

Yup, that's it.

Shouldn't it make sense to ONLY include disable-write.inc in profiles that DO NOT have disable-mnt?

This makes the progiles easier, as disable-write-mnt has no effect.

@rusty-snake commented on GitHub (Dec 11, 2020): > I am wondering if I understand the difference/relationship between disable-mnt and (including) disable-write.inc correctly. The former blacklists /media, /mnt, /run/media and /run/mount access, while the latter makes those exact same directories read-only. Yup, that's it. > Shouldn't it make sense to ONLY include disable-write.inc in profiles that DO NOT have disable-mnt? This makes the progiles easier, as disable-write-mnt has no effect.

gitea-mirror commented

2026-05-05 09:05:06 -06:00

Author

Owner

@ghost commented on GitHub (Dec 11, 2020):

This makes the progiles easier, as disable-write-mnt has no effect.

Makes more sense now. Thanks!

@ghost commented on GitHub (Dec 11, 2020): > This makes the progiles easier, as disable-write-mnt has no effect. Makes more sense now. Thanks!

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#2405

No description provided.

Rows
Columns