github-starred/firejail

Fork 0

mirror of https://github.com/netblue30/firejail.git synced 2026-05-15 14:16:14 -06:00

[GH-ISSUE #402] Add recursive read-only option #289

New issue

Closed

opened 2026-05-05 05:32:12 -06:00 by gitea-mirror · 5 comments

gitea-mirror commented

2026-05-05 05:32:12 -06:00

Owner

Originally created by @nick75e on GitHub (Apr 1, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/402

Hi!

read-only is only effective for the indicated directory leaving all sub-directories and sub-files unprotected.
Can you create another option like read-only.all <folder> which would protect everything.

Thanks.

Originally created by @nick75e on GitHub (Apr 1, 2016). Original GitHub issue: https://github.com/netblue30/firejail/issues/402 Hi! `read-only` is only effective for the indicated directory leaving all sub-directories and sub-files unprotected. Can you create another option like `read-only.all <folder>` which would protect everything. Thanks.

gitea-mirror

2026-05-05 05:32:12 -06:00

closed this issue
added the
information_old
label

gitea-mirror commented

2026-05-05 05:32:17 -06:00

Author

Owner

@netblue30 commented on GitHub (Apr 2, 2016):

This is how is working in this moment, read-only is recursive.

@netblue30 commented on GitHub (Apr 2, 2016): This is how is working in this moment, read-only is recursive.

gitea-mirror commented

2026-05-05 05:32:18 -06:00

Author

Owner

@nick75e commented on GitHub (Apr 2, 2016):

This is how is working in this moment, read-only is recursive.

I didn't understand your statement until I tested again and yes you're right but only for the home directory.
It doesn't work like that with mounted hard drives. When I use read-only /media where all non-system disks are, directories are still writeable.
It'd work only if I did that for each and every directory!

@nick75e commented on GitHub (Apr 2, 2016): > This is how is working in this moment, read-only is recursive. I didn't understand your statement until I tested again and yes you're right but only for the home directory. It doesn't work like that with mounted hard drives. When I use `read-only /media` where all non-system disks are, directories are still writeable. It'd work only if I did that for each and every directory!

gitea-mirror commented

2026-05-05 05:32:20 -06:00

Author

Owner

@nick75e commented on GitHub (Apr 2, 2016):

EDIT: adding read-only /media/* does the trick.
Sorry for the bother.

@nick75e commented on GitHub (Apr 2, 2016): EDIT: adding `read-only /media/*` does the trick. Sorry for the bother.

gitea-mirror commented

2026-05-05 05:32:21 -06:00

Author

Owner

@netblue30 commented on GitHub (Apr 3, 2016):

No problem.

@netblue30 commented on GitHub (Apr 3, 2016): No problem.

gitea-mirror commented

2026-05-05 05:32:23 -06:00

Author

Owner

@ghost commented on GitHub (Apr 6, 2016):

I think #158 is related and explains it.

@ghost commented on GitHub (Apr 6, 2016): I think #158 is related and explains it.

gitea-mirror referenced this issue

2026-05-05 10:04:07 -06:00

[PR #289] [MERGED] Fix problem with relative path in storage_find function #3585

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#289

No description provided.

Rows
Columns