github-starred/firejail

Fork 0

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

[GH-ISSUE #2071] [bug] Whitelisting a file leads to inability to write to it #1399

New issue

Closed

opened 2026-05-05 08:03:46 -06:00 by gitea-mirror · 4 comments

gitea-mirror commented

2026-05-05 08:03:46 -06:00

Owner

Originally created by @chiraag-nataraj on GitHub (Jul 28, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2071

Currently running firejail 0.9.55. When I whitelist a file (not a directory), I get errors like "Couldn't write to file" (when I whitelisted ~/.config/akregatorrc). I got similar errors from Google Earth [Pro] as well. I'm going to try to investigate, but just wanted to put this on the radar.

Originally created by @chiraag-nataraj on GitHub (Jul 28, 2018). Original GitHub issue: https://github.com/netblue30/firejail/issues/2071 Currently running firejail 0.9.55. When I whitelist a file (not a directory), I get errors like "Couldn't write to file" (when I whitelisted `~/.config/akregatorrc`). I got similar errors from Google Earth [Pro] as well. I'm going to try to investigate, but just wanted to put this on the radar.

gitea-mirror

2026-05-05 08:03:46 -06:00

closed this issue
added the
bug
label

gitea-mirror commented

2026-05-05 08:03:48 -06:00

Author

Owner

@chiraag-nataraj commented on GitHub (Jul 28, 2018):

Apparently the program gets an EBUSY when it tries to rename a temporary file (which it actually writes to) to the actual configuration file. Is there any way to deal with this besides just whitelisting the entire .config directory?

@chiraag-nataraj commented on GitHub (Jul 28, 2018): Apparently the program gets an `EBUSY` when it tries to rename a temporary file (which it actually writes to) to the actual configuration file. Is there any way to deal with this besides just whitelisting the entire `.config` directory?

gitea-mirror commented

2026-05-05 08:03:49 -06:00

Author

Owner

@smitsohu commented on GitHub (Jul 29, 2018):

Is this possibly the same as #1793 and #1355?

@smitsohu commented on GitHub (Jul 29, 2018): Is this possibly the same as #1793 and #1355?

gitea-mirror commented

2026-05-05 08:03:51 -06:00

Author

Owner

@chiraag-nataraj commented on GitHub (Jul 29, 2018):

Yes, I think so. This seems to be an issue with certain programs which write a temp file before moving it to the actual location.

@chiraag-nataraj commented on GitHub (Jul 29, 2018): Yes, I think so. This seems to be an issue with certain programs which write a temp file before moving it to the actual location.

gitea-mirror commented

2026-05-05 08:03:52 -06:00

Author

Owner

@chiraag-nataraj commented on GitHub (Dec 9, 2018):

Closing since this seems to be a dup of some of the others.

@chiraag-nataraj commented on GitHub (Dec 9, 2018): Closing since this seems to be a dup of some of the others.

gitea-mirror referenced this issue

2026-05-05 10:10:50 -06:00

[PR #1399] [MERGED] Private /lib feature #3943

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

No description provided.

Rows
Columns