#11676: sage-pkg does not force world-readable permissions
-------------------------------+--------------------------------------------
Reporter: AlexanderDreyer | Owner: AlexanderDreyer
Type: enhancement | Status: needs_info
Priority: major | Milestone: sage-duplicate/invalid/wontfix
Component: scripts | Keywords: chmod umask install mode
Work_issues: | Upstream: N/A
Reviewer: | Author: Alexander Dreyer
Merged: | Dependencies:
-------------------------------+--------------------------------------------
Comment(by AlexanderDreyer):
Replying to [comment:31 leif]:
> So I wouldn't mind if `sage -pkg` issued warnings (to perhaps be
disabled by some option), but the proper or safest way to avoid such
issues is IMHO still to set the umask and do a `chmod -R` on `src/` at
least (from `sage-spkg`), although this will in most cases be redundant or
superfluous (e.g. if `install -c -m ...` is used by the spkg anyway, or
all files to be copied with `cp -p` already have the proper permissions).
In fact, a sanity check should be made ''on the Sage installation'', after
one or more (or all) spkgs have been built and installed.
umask alone is not enough, the standalone file server, where my projects
live, is configured to override the user's umask and enforces world-
writable permissions. Installed files should not preserve them, so install
(or something equivalent) is necessary indeed.
chmod is not work always be effective. For instance, think of working on a
FAT-based USB-drive. The latter has fixed permissions, set on mount time.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11676#comment:32>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
