commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mladen Turk (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DAEMON-178) jsvc process does not take the umask of the running user. It is always 077
Date Sat, 16 Oct 2010 11:25:25 GMT

    [ https://issues.apache.org/jira/browse/DAEMON-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921678#action_12921678
] 

Mladen Turk commented on DAEMON-178:
------------------------------------

Added support to specify the umask at compile time.
Eg.

make EXTRA_CFLAGS="-DJSVC_UMASK=022" will use umask(022)
It is even possible to
make EXTRA_CFLAGS="-DJSVC_UMASK=002"

In that case the following will appear in the log:
NOTICE: jsvc umask of 002 allows write permission to group and/or other

This is similar technique Apache suexec is using.



> jsvc process does not take the umask of the running user. It is always 077
> --------------------------------------------------------------------------
>
>                 Key: DAEMON-178
>                 URL: https://issues.apache.org/jira/browse/DAEMON-178
>             Project: Commons Daemon
>          Issue Type: Bug
>          Components: Jsvc
>    Affects Versions: 1.0.3
>         Environment: Ubuntu Hardy 8.0.4, jdk1.6.2
>            Reporter: J Miller
>
> 1) create a simple implementation of the Daemon interface that writes "hello world" log
files
> 2) compile jsvc as described in the documentation
> 3) verify that your linux user has umask != 077, by typing "umask"
> 4) start jsvc with all the required CP args as described in the documentation
> 5) look the log file permissions
> Expected: The permissions are not 700.
> Actual: They are 700.
> 6) Modify commons-daemon/src/native/unix/native/jsvc-unix.c, replacing 077 with 022
> 7) recompile jsvc
> 8) repeat 4-5
> Expected: The permissions are 755.
> Actual: The permissions are 755.
> Conclusion: The jsvc process uses a hard-coded value, instead of adopting the running
user's umask, as expected.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message