[GH-ISSUE #1168] Setting rlimit-fsize to 4GB fails #800

New issue

Closed

opened 2026-05-05 06:52:19 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 06:52:19 -06:00

Owner

Originally created by @filippog on GitHub (Mar 28, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1168

Hi,
we've run into an issue with rlimit-fsize in firejail profiles while set to 4294967296 bytes, firejail would refuse to start with failure to set seccomp filter.
Upon investigation it seems the issue lies with sscanf using %u to scan the config file value, as far as I can tell, what do you think?

Originally created by @filippog on GitHub (Mar 28, 2017). Original GitHub issue: https://github.com/netblue30/firejail/issues/1168 Hi, we've run into an issue with `rlimit-fsize` in firejail profiles while set to `4294967296` bytes, firejail would refuse to start with failure to set seccomp filter. Upon investigation it seems the issue lies with `sscanf` using `%u` to scan the config file value, as far as I can tell, what do you think?

gitea-mirror

2026-05-05 06:52:19 -06:00

closed this issue
added the
bug
label

gitea-mirror commented

2026-05-05 06:52:25 -06:00

Author

Owner

@netblue30 commented on GitHub (Mar 28, 2017):

Fixed on mainline, thank you for the bug. It was a 32-bit vs 64-bit problem.

@netblue30 commented on GitHub (Mar 28, 2017): Fixed on mainline, thank you for the bug. It was a 32-bit vs 64-bit problem.

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

No description provided.

Rows
Columns