New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow running Sage.app by someone other than it was installed by #11755
Comments
comment:1
That's a matter of the current umask, but we could of course change the file permission on updates to that file. On the other hand, opening an existing file for writing shouldn't change the permissions in the first place. If the file gets deleted inbetween, an ordinary user would also need write permissions on the directory the file is located / recreated in, i.e. It's not immediately clear to me why an ordinary user would have to move Sage though, just to run the application. (But I don't use apples.) Allowing the group to write to this file would certainly be better, putting potential users (that move the installation) into that group. (But they still won't be able to actually modify / fix hardcoded paths, which is the whole purpose of The whole issue might be related to #5852 (and previously #11707), such that after this ticket is resolved, changing the permissions may no longer be necessary. |
comment:3
Replying to @nexttime:
If an ordinary user moves Sage, then presumably they have write permissions to the new SAGE_ROOT/local/lib, so there won't be any problems, will there? This all happens in the script In fact, I posted a patch doing some of this (it doesn't print the warning) at #5155. Perhaps we should try to fix this issue here and deal with the other issues from #5155 there. |
This comment has been minimized.
This comment has been minimized.
Changed keywords from mac app to mac app SAGE_ROOT |
Dependencies: #21783 |
comment:9
Outdated, should be closed |
comment:11
Sure. |
Since Sage.app checks if it moved every time upon startup, any user who runs the application needs to be able to write to
local/lib/sage-current-location.txt
. This files seems to default to 0644 permissions.We can either change the Sage.app code so that it doesn't need to check every time or make the file world writable.
Relevant comments from #5852:
jdemeyer said:
leif said:
Depends on #31270
CC: @kcrisman @dimpase
Component: relocation
Keywords: mac app SAGE_ROOT
Issue created by migration from https://trac.sagemath.org/ticket/11755
The text was updated successfully, but these errors were encountered: