Restrictive umask and permissions may cause a built snap to be unusable
Metadata
Current evaluation
Closed without resolution. The report regarding restrictive umask causing unusable snaps was abandoned due to inactivity. No permission validation or umask enforcement was implemented in snapcraft.
Suggested action: —
No scores available.
Issue body
I use the umask 007 in my system.
When I built a test package with snapcraft and installed it in a Snappy Core system, most of the files and folders of the package where not accessible by the "other" users, and thus I couldn't run the binaries (no permission).
I think snappy/snapcraft should make some permissions/umask checks.
Maybe snapcraft or "snappy build" should check the permissions of all packaged files and directories (like how the Debian build tools do), and either correct the permissions or warn the user about files that have strange permissions.
Snapcraft could also enforce an umask of 002 or 022.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The report regarding restrictive umask causing unusable snaps was abandoned due to inactivity. No permission validation or umask enforcement was implemented in snapcraft. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The umask permission handling request was abandoned without snapcraft implementing automatic permission checks or umask enforcement. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution or comments. The report regarding restrictive umask causing unusable snaps was abandoned due to inactivity. No permission checks or umask enforcement were implemented. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1871109 snapcraft should check file creation permissions and warn/error out instead of generating a non-functional snap | snapcraft (launchpad) | closed | Closed without resolution. The requested permission checks were not implemented, and the issue remains abandoned. |