Introduction
This extension allows better control over the initial permissions of files created by buildout by allowing the umask used by the buildout script to be specified in the configuration file.
Because of bug 180705 of zc.buildout, this doesn’t work for scripts installed by buildout.
This doesn’t affect the umask of other scripts in the buildout, unless they set their own the umask of the user running them will be used, e.g.: ZEO/Zope might still make var/filestore/Datafile.fs world readable if your umask is 022.
Usage
[buildout] extensions = buildout.umask umask = 027
The umask parameter can be specified using any of Python conventions for numeric literals of binary, octal, decimal or hexadecimal radix. If any of them is used and a 0 is the first digit, octal is assumed as well.
Questions
The code is quite simple, take a glimpse.
Bugs
Changelog
0.5.2 (2010-12-02)
Documentation fixes.
0.5.1 (2010-12-02)
Fix packaging by using setuptools_bzr.
0.5 (2010-12-01)
First public release
0.1 (unreleased)
Initial version.
1 maintainer
Metadata
1 maintainer
Release files for buildout.umask 0.5.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| buildout.umask-0.5.2.tar.gz | 2.7 kB | Without provenance | Details for buildout.umask-0.5.2.tar.gz |
Release files / buildout.umask-0.5.2.tar.gz
| Download URL | buildout.umask-0.5.2.tar.gz |
|---|---|
| Size | 2.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eb2b342ee3f204406a7473d6953cf524bbe652040892f2e427ce1e2e4a101c71
|
|
BLAKE2b-256 checksum How to use checksums |
034f80a1540ce603234e10c10fe9ee34ce2437f3ad6e0136c476132f0fc52236
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for buildout.umask 0.5.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
