Unix Permission Workbench
Translate declared Unix mode bits and calculate a no-default-ACL umask creation result without touching a filesystem.
Loading tool…
How to use Unix Permission Workbench
Translate declared Unix mode bits and calculate a no-default-ACL umask creation result without touching a filesystem. Inspect owner/group/other permissions, special-bit symbols and an explicit class query. Keep file creation masking separate from interpreting an existing chmod mode.
- Provide mode: octal or nine permission characters, creation umask in octal, requested creation permissions in octal.
- Choose the supported mode and run the tool. Review its assumptions and any reported errors.
- Copy the result or download a separate output; reset to clear the current form.
Good to know
- Mode input is 3–4 octal digits 0000–7777, or exactly nine rwx permission characters with s/S in owner/group execute positions and t/T in other execute position. There is no file-type prefix, chmod clause parser, relative symbolic command or real chmod call.
- Creation request and mask are separately limited to 0000–0777. The calculation clears masked permission bits from the explicit request; it does not add execute permissions. Special bits are excluded from that creation calculation. A parent default ACL is assumed absent.
- The selected Owner/Group/Other class is supplied by you; it does not look up identities or combine group memberships. Actual ACLs, supplementary groups, root/capabilities, mount flags, directory traversal, sticky deletion rules, operating-system set-ID clearing and security policies are not assessed.
- The report shows special bits and their symbols but does not guarantee those bits will be retained or applied by a real filesystem. Read/write/execute bits are not a recommendation to loosen permissions. Inputs are capped at 100 characters per control.
- No file path is opened, permission changed, shell command executed or system information discovered. Use the displayed arithmetic as a review aid, then consult the target system’s actual policy.
- Structured text output is limited to 500,000 characters. Reduce the supplied source when that separate output budget is exceeded.
- Inputs are processed on this device and are not automatically saved or uploaded.
Common questions
Does umask turn an existing 0755 file into a new mode?
No. The umask calculation here concerns creation with an explicit requested mode and no default ACL. Existing mode decoding is a separate calculation. Actual access can also depend on ACLs, identities, parent directories and operating-system privileges that this tool does not inspect.
Does this change my original input?
No. The tool returns a separate result. Review that output before using it in another application.
Keep going with related tools
All developer →Windows Export Path Checker
Inspect supplied relative path strings for a conservative Windows export naming profile.
DeveloperGit Attributes Resolution Workbench
Trace selected Git attribute states across supplied virtual .gitattributes files, including source precedence and the built-in binary macro.
DeveloperPOSIX Relative Path Workbench
Calculate normalized absolute targets, relative routes and common ancestors from an explicit POSIX-style base path.