The checkperms module is accessible via the paste.script module.
Currently only supports Posix systems (with Posixy permissions). Permission stuff can probably be stubbed out later.
[(2048, 'setuid bit', 'setuid bit: make contents owned by directory owner'), (1024, 'setgid bit', 'setgid bit: make contents inherit permissions from directory'), (512, 'sticky bit', 'sticky bit: append-only directory'), (256, 'read by owner', 'read by owner'), (128, 'write by owner', 'write by owner'), (64, 'execute by owner', 'owner can search directory'), (32, 'allow read by group members', 'allow read by group members'), (16, 'allow write by group members', 'allow write by group members'), (8, 'execute by group members', 'group members can search directory'), (4, 'read by others', 'read by others'), (2, 'write by others', 'write by others'), (1, 'execution by others', 'others can search directory')]
Reads a spec like 'rw-r--r--' into a octal number suitable for chmod. That is characters in groups of three -- first group is user, second for group, third for other (all other people). The characters are r (read), w (write), and x (executable), though the executable can also be s (sticky). Files in sticky directories get the directories permission setting.
Examples:
>>> print oct(read_perm_spec('rw-r--r--'))
0644
>>> print oct(read_perm_spec('rw-rwsr--'))
02664
>>> print oct(read_perm_spec('r-xr--r--'))
0544
>>> print oct(read_perm_spec('r--------'))
0400
Gives the difference between the actual mode of the file and the given mode. If keep_exe is true, then if the mode doesn't include any executable information the executable information will simply be ignored. High bits are also always ignored (except suid/sgid and sticky bit).
Returns a list of differences (empty list if no differences)
Calculates the new mode given the current node cur_mode and the mode spec mode and if keep_exe is true then also keep the executable bits in cur_mode if mode has no executable bits in it. Return the new mode.
Examples:
>>> print oct(calc_set_mode(0775, 0644)) 0755 >>> print oct(calc_set_mode(0775, 0744)) 0744 >>> print oct(calc_set_mode(010600, 0644)) 010644 >>> print oct(calc_set_mode(0775, 0644, False)) 0644
Calculates what a string spec means, returning (uid, username, gid, groupname), where there can be None values meaning no preference.
The spec is a string like owner:group. It may use numbers instead of user/group names. It may leave out :group. It may use '-' to mean any-user/any-group.
Return a list of differences between the ownership of filename and the spec given.
Represents a set of specifications for permissions.
Typically reads from a file that looks like this:
rwxrwxrwx user:group filename
If the filename ends in /, then it expected to be a directory, and the directory is made executable automatically, and the contents of the directory are given the same permission (recursively). By default the executable bit on files is left as-is, unless the permissions specifically say it should be on in some way.
You can use 'nomodify filename' for permissions to say that any permission is okay, and permissions should not be changed.
Use 'noexist filename' to say that a specific file should not exist.
Use 'symlink filename symlinked_to' to assert a symlink destination
The entire file is read, and most specific rules are used for each file (i.e., a rule for a subdirectory overrides the rule for a superdirectory). Order does not matter.
This class contains 10 members.
See the source for more information.