[JIRA] Created: (HUDSON-5114) hardcoded umask in com.sun.akuma/Daemon.java

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

[JIRA] Created: (HUDSON-5114) hardcoded umask in com.sun.akuma/Daemon.java

Hudson issues mailing list
hardcoded umask in com.sun.akuma/Daemon.java
--------------------------------------------

                 Key: HUDSON-5114
                 URL: http://issues.hudson-ci.org/browse/HUDSON-5114
             Project: Hudson
          Issue Type: Bug
    Affects Versions: current
         Environment: RHEL 5.4
            Reporter: sgoodliff
            Priority: Minor



Hello,

When running hudson via winstone as below.

/usr/lib/jvm/java-1.6.0/bin/java -Dcom.sun.akuma.Daemon=daemonized -Djava.awt.headless=true -DHUDSON_HOME=/var/lib/hudson -jar /usr/lib/hudson/hudson.war --logfile=/var/log/hudson/hudson.log --daemon --httpPort=8080 --debug=9 --handlerCountMax=100 --handlerCountMaxIdle=20

The umask of all the files created are set as 027 rather than the user who invokes the processes umask.

For example a user with a umask of 022 runs hudson and a job and all the resulting files are set to 027.

This is because the Daemon.java file that is part of akuma has a call to

    LIBC.umask(0027);

Please can this be made user configurable or use the inherent umask of the running user.

Thanks

Steve Goodliff


--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-5114) hardcoded umask in com.sun.akuma/Daemon.java

Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-5114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137836#action_137836 ]

brucepainter commented on HUDSON-5114:
--------------------------------------

We are encountering this same issue with Hudson 1.353, and it is actually a big issue for us.
It would be great if this could be changed soon, or at least a workaround published.

We are looking at having to move our build process into shell scripts and then just have those shell scripts launched by the Hudson build process with the hope that it resolves this issue.

> hardcoded umask in com.sun.akuma/Daemon.java
> --------------------------------------------
>
>                 Key: HUDSON-5114
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-5114
>             Project: Hudson
>          Issue Type: Bug
>    Affects Versions: current
>         Environment: RHEL 5.4
>            Reporter: sgoodliff
>            Priority: Minor
>
> Hello,
> When running hudson via winstone as below.
> /usr/lib/jvm/java-1.6.0/bin/java -Dcom.sun.akuma.Daemon=daemonized -Djava.awt.headless=true -DHUDSON_HOME=/var/lib/hudson -jar /usr/lib/hudson/hudson.war --logfile=/var/log/hudson/hudson.log --daemon --httpPort=8080 --debug=9 --handlerCountMax=100 --handlerCountMaxIdle=20
> The umask of all the files created are set as 027 rather than the user who invokes the processes umask.
> For example a user with a umask of 022 runs hudson and a job and all the resulting files are set to 027.
> This is because the Daemon.java file that is part of akuma has a call to
>     LIBC.umask(0027);
> Please can this be made user configurable or use the inherent umask of the running user.
> Thanks
> Steve Goodliff

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-5114) hardcoded umask in com.sun.akuma/Daemon.java

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-5114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138607#action_138607 ]

olo commented on HUDSON-5114:
-----------------------------

We have the same problem; the sites generated by Maven site build are all initially inaccessible to Apache server until we launch chmod. We've placed it as a shell build step, but it's a dirty workaround and it took some time to figure out.

Setting hardcoded umask is a silly thing when done en masse and should only be performed temporarily, for really security critical tasks (like the process creating some temporary file with a private key).



> hardcoded umask in com.sun.akuma/Daemon.java
> --------------------------------------------
>
>                 Key: HUDSON-5114
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-5114
>             Project: Hudson
>          Issue Type: Bug
>    Affects Versions: current
>         Environment: RHEL 5.4
>            Reporter: sgoodliff
>            Priority: Minor
>
> Hello,
> When running hudson via winstone as below.
> /usr/lib/jvm/java-1.6.0/bin/java -Dcom.sun.akuma.Daemon=daemonized -Djava.awt.headless=true -DHUDSON_HOME=/var/lib/hudson -jar /usr/lib/hudson/hudson.war --logfile=/var/log/hudson/hudson.log --daemon --httpPort=8080 --debug=9 --handlerCountMax=100 --handlerCountMaxIdle=20
> The umask of all the files created are set as 027 rather than the user who invokes the processes umask.
> For example a user with a umask of 022 runs hudson and a job and all the resulting files are set to 027.
> This is because the Daemon.java file that is part of akuma has a call to
>     LIBC.umask(0027);
> Please can this be made user configurable or use the inherent umask of the running user.
> Thanks
> Steve Goodliff

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Updated: (HUDSON-5114) hardcoded umask in com.sun.akuma/Daemon.java

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

     [ http://issues.hudson-ci.org/browse/HUDSON-5114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

mindless updated HUDSON-5114:
-----------------------------

    Description:
Hello,

When running hudson via winstone as below.

/usr/lib/jvm/java-1.6.0/bin/java -Dcom.sun.akuma.Daemon=daemonized -Djava.awt.headless=true -DHUDSON_HOME=/var/lib/hudson -jar /usr/lib/hudson/hudson.war --logfile=/var/log/hudson/hudson.log --daemon --httpPort=8080 --debug=9 --handlerCountMax=100 --handlerCountMaxIdle=20

The umask of all the files created are set as 027 rather than the user who invokes the processes umask.

For example a user with a umask of 022 runs hudson and a job and all the resulting files are set to 027.

This is because the Daemon.java file that is part of akuma has a call to

    LIBC.umask(0027);

Please can this be made user configurable or use the inherent umask of the running user.

Thanks

Steve Goodliff


  was:

Hello,

When running hudson via winstone as below.

/usr/lib/jvm/java-1.6.0/bin/java -Dcom.sun.akuma.Daemon=daemonized -Djava.awt.headless=true -DHUDSON_HOME=/var/lib/hudson -jar /usr/lib/hudson/hudson.war --logfile=/var/log/hudson/hudson.log --daemon --httpPort=8080 --debug=9 --handlerCountMax=100 --handlerCountMaxIdle=20

The umask of all the files created are set as 027 rather than the user who invokes the processes umask.

For example a user with a umask of 022 runs hudson and a job and all the resulting files are set to 027.

This is because the Daemon.java file that is part of akuma has a call to

    LIBC.umask(0027);

Please can this be made user configurable or use the inherent umask of the running user.

Thanks

Steve Goodliff


    Component/s: core

> hardcoded umask in com.sun.akuma/Daemon.java
> --------------------------------------------
>
>                 Key: HUDSON-5114
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-5114
>             Project: Hudson
>          Issue Type: Bug
>          Components: core
>    Affects Versions: current
>         Environment: RHEL 5.4
>            Reporter: sgoodliff
>            Priority: Minor
>
> Hello,
> When running hudson via winstone as below.
> /usr/lib/jvm/java-1.6.0/bin/java -Dcom.sun.akuma.Daemon=daemonized -Djava.awt.headless=true -DHUDSON_HOME=/var/lib/hudson -jar /usr/lib/hudson/hudson.war --logfile=/var/log/hudson/hudson.log --daemon --httpPort=8080 --debug=9 --handlerCountMax=100 --handlerCountMaxIdle=20
> The umask of all the files created are set as 027 rather than the user who invokes the processes umask.
> For example a user with a umask of 022 runs hudson and a job and all the resulting files are set to 027.
> This is because the Daemon.java file that is part of akuma has a call to
>     LIBC.umask(0027);
> Please can this be made user configurable or use the inherent umask of the running user.
> Thanks
> Steve Goodliff

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-5114) hardcoded umask in com.sun.akuma/Daemon.java

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-5114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=141293#action_141293 ]

brucepainter commented on HUDSON-5114:
--------------------------------------

We have come up with a workaround solution for this as well, but are now finding that this is impacting other groups in our organization now that we are upgrading them from old versions of Hudson.

Is this something that can be addressed?  
How can we go about getting some traction on this issue?

> hardcoded umask in com.sun.akuma/Daemon.java
> --------------------------------------------
>
>                 Key: HUDSON-5114
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-5114
>             Project: Hudson
>          Issue Type: Bug
>          Components: core
>    Affects Versions: current
>         Environment: RHEL 5.4
>            Reporter: sgoodliff
>            Priority: Minor
>
> Hello,
> When running hudson via winstone as below.
> /usr/lib/jvm/java-1.6.0/bin/java -Dcom.sun.akuma.Daemon=daemonized -Djava.awt.headless=true -DHUDSON_HOME=/var/lib/hudson -jar /usr/lib/hudson/hudson.war --logfile=/var/log/hudson/hudson.log --daemon --httpPort=8080 --debug=9 --handlerCountMax=100 --handlerCountMaxIdle=20
> The umask of all the files created are set as 027 rather than the user who invokes the processes umask.
> For example a user with a umask of 022 runs hudson and a job and all the resulting files are set to 027.
> This is because the Daemon.java file that is part of akuma has a call to
>     LIBC.umask(0027);
> Please can this be made user configurable or use the inherent umask of the running user.
> Thanks
> Steve Goodliff

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [JIRA] Commented: (HUDSON-5114) hardcoded umask in com.sun.akuma/Daemon.java

Steven Goodliff
Hi,

AFAIK,

 It just needs that line commenting out in the Akuma code and then the Hudson guys to use the version that has the line commented out.

you could try its project page but it doesn't seem to get much activity

https://akuma.dev.java.net/servlets/ProjectMailingListList


On 26 August 2010 17:19, [hidden email] (JIRA) <[hidden email]> wrote:

   [ http://issues.hudson-ci.org/browse/HUDSON-5114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=141293#action_141293 ]

brucepainter commented on HUDSON-5114:
--------------------------------------

We have come up with a workaround solution for this as well, but are now finding that this is impacting other groups in our organization now that we are upgrading them from old versions of Hudson.

Is this something that can be addressed?
How can we go about getting some traction on this issue?

> hardcoded umask in com.sun.akuma/Daemon.java
> --------------------------------------------
>
>                 Key: HUDSON-5114
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-5114
>             Project: Hudson
>          Issue Type: Bug
>          Components: core
>    Affects Versions: current
>         Environment: RHEL 5.4
>            Reporter: sgoodliff
>            Priority: Minor
>
> Hello,
> When running hudson via winstone as below.
> /usr/lib/jvm/java-1.6.0/bin/java -Dcom.sun.akuma.Daemon=daemonized -Djava.awt.headless=true -DHUDSON_HOME=/var/lib/hudson -jar /usr/lib/hudson/hudson.war --logfile=/var/log/hudson/hudson.log --daemon --httpPort=8080 --debug=9 --handlerCountMax=100 --handlerCountMaxIdle=20
> The umask of all the files created are set as 027 rather than the user who invokes the processes umask.
> For example a user with a umask of 022 runs hudson and a job and all the resulting files are set to 027.
> This is because the Daemon.java file that is part of akuma has a call to
>     LIBC.umask(0027);
> Please can this be made user configurable or use the inherent umask of the running user.
> Thanks
> Steve Goodliff

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira