github-starred/firejail

Fork 0

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

[GH-ISSUE #222] `make install` creates files with wrong permissions when using non-standard umask #154

New issue

Closed

opened 2026-05-05 05:11:40 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 05:11:40 -06:00

Owner

Originally created by @genodeftest on GitHub (Jan 12, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/222

Steps to reproduce:

set umask to something more permissive, e.g. 0077 for both user and root
configure, make and sudo make install

What happens:
/usr/local/lib/firejail is not accessible by user. Same is true for most other folders created by make install, including /usr/local/share/bash-completion and /usr/local/etc/firejail

Possible solution:
specify --mode=755 for mkdir in Makefile.in
The mkdeb.sh, mkman.sh and mketc.sh files might require additional steps.

Originally created by @genodeftest on GitHub (Jan 12, 2016). Original GitHub issue: https://github.com/netblue30/firejail/issues/222 Steps to reproduce: 1. set umask to something more permissive, e.g. 0077 for both user and root 2. configure, make and sudo make install What happens: /usr/local/lib/firejail is not accessible by user. Same is true for most other folders created by `make install`, including /usr/local/share/bash-completion and /usr/local/etc/firejail Possible solution: specify `--mode=755` for `mkdir` in Makefile.in The mkdeb.sh, mkman.sh and mketc.sh files might require additional steps.

gitea-mirror

2026-05-05 05:11:40 -06:00

closed this issue
added the
bug
label

gitea-mirror commented

2026-05-05 05:11:46 -06:00

Author

Owner

@netblue30 commented on GitHub (Jan 14, 2016):

Fixed, thanks!

@netblue30 commented on GitHub (Jan 14, 2016): Fixed, thanks!

gitea-mirror commented

2026-05-05 05:11:50 -06:00

Author

Owner

@genodeftest commented on GitHub (Jan 14, 2016):

Thank, that was fast ;)

@genodeftest commented on GitHub (Jan 14, 2016): Thank, that was fast ;)

gitea-mirror commented

2026-05-05 05:11:51 -06:00

Author

Owner

@ghost commented on GitHub (Jan 31, 2016):

The same could have probably been achieved by putting "Defaults umask_override" in /etc/sudoers. This umask thing needs to get more popular.

From man sudoers:

If set, sudo will set the umask as specified by sudoers without modification. This makes it possible to specify a more permissive umask in sudoers than the user's own umask and matches historical behavior. If umask_override is not set, sudo will set the umask to be the union of the user's umask and what is specified in sudoers. This flag is off by default.

@ghost commented on GitHub (Jan 31, 2016): The same could have probably been achieved by putting "Defaults umask_override" in /etc/sudoers. This umask thing needs to get more popular. From man sudoers: > If set, sudo will set the umask as specified by sudoers without modification. This makes it possible to specify a more permissive umask in sudoers than the user's own umask and matches historical behavior. If umask_override is not set, sudo will set the umask to be the union of the user's umask and what is specified in sudoers. This flag is off by default.

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

No description provided.

Rows
Columns

[GH-ISSUE #222] make install creates files with wrong permissions when using non-standard umask #154

[GH-ISSUE #222] `make install` creates files with wrong permissions when using non-standard umask #154