Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
Debian-based GNU/Linux
Description
Our Apache server is proxying Hudson, while serving its static content directly.
As Apache workers are run by user www-data and group www-data, they're not entitled to access /var/run/hudson and /var/lib/hudson since they're only group readable (hudson:adm).
This comes from the fact the .deb package postinst script performs:
- chown hudson:adm on /var/run/hudson and /var/lib/hudson. Why "adm"?
- chmod 750 on /var/run/hudson and /var/lib/hudson. Why not user readable?
Could you please amend the postinst script so that:
- either it just set access rights at first installation time, so that my custom changes are not reset at upgrade time.
- or it uses: chmod 755.
- or it uses: chown hudson:www-data.
- or, simpler, it doesn't deal with such things at all.
Thanks.
Attachments
Issue Links
- is related to
-
JENKINS-4047 Debian package sets wrong permissions on /var/lib/hudson/.ssh
-
- Resolved
-
-
JENKINS-5969 Problematic chown/chmod at Debian package upgrade
-
- Resolved
-
-
JENKINS-5771 Debian package upgrade sets wrong user permissions if HUDSON_USER is not hudson (default)
-
- Resolved
-
Activity
Field | Original Value | New Value |
---|---|---|
Link |
This issue is related to |
Link |
This issue is related to |
Link |
This issue is related to |
Assignee | ashlux [ ashlux ] | Kohsuke Kawaguchi [ kohsuke ] |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Resolved [ 5 ] |
Component/s | other [ 15490 ] | |
Component/s | infrastructure [ 15687 ] |
Status | Resolved [ 5 ] | Closed [ 6 ] |
Workflow | JNJira [ 137674 ] | JNJira + In-Review [ 204568 ] |
Not reseting owners and access rights seems to form a consensus.