Last modified: 2013-06-10 21:57:22 UTC
They may contain passwords etc. in, for example, stack traces.
http://marc.info/?l=grid-engine-users&m=112448326118257&w=2 (NB: from 2005, but I didn't find anything more current) suggests that the permissions are hardcoded in SGE. But a small test ("jsub true"; "chmod 600 ~/true.{err,out} && jsub true") showed that SGE doesn't change permissions if the error and outputs file already exist. So technically it seems to be possible to preemptively touch the error and output files. However, a quick fix has the potential to severely disrupt jobs of users like me :-) who point "-o" to a directory. So I'll think about a patch that considers these different use cases till next week. My initial idea would be: If the error and/or output file do not exist: If the user supplied a "-umask" option: "umask (oct ($umask));" Else: If we are a tool account: "umask (0007);" Else: "umask (0077);" If $stderr: Open and close error and output files. Else: Redirect STDOUT/STDERR to them. This would provide a sensible default (if a user has no opinion, make the output rw------- for users and rw-rw---- for tools), doesn't override the user's action outside of SGE (i. e., "chmod") and allows them to specify permissions for new logs in a clear way.
this is potential security issue, however there exist workaround as you can specify the output directory (which can just be not readable for others) should be resolved quickly
boosting - no response for weeks and this is a security issue
I can't seem to think of a scenario where a -umask option would make sense (as opposed to, you know, just setting umask).
(In reply to comment #4) > I can't seem to think of a scenario where a -umask option would make sense > (as > opposed to, you know, just setting umask). If I want to make output files world-readable, and jsub sets umask to 0007/0077, how could I relax that by setting umask?!
Fixed by https://gerrit.wikimedia.org/r/#/c/67644/ Will be made avaliable next update of jobutils
