Bug 998041 - Rubygem-passenger doesn't account for system umask when creating tmp directories
Summary: Rubygem-passenger doesn't account for system umask when creating tmp directories
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: rubygem-passenger
Version: el6
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Brett Lentz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-16 20:17 UTC by Jamie Duncan
Modified: 2020-11-30 15:15 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-30 15:15:29 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
accounts for umask (778 bytes, patch)
2013-08-16 20:20 UTC, Jamie Duncan
no flags Details | Diff

Description Jamie Duncan 2013-08-16 20:17:14 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0
Build Identifier: 

rubygem-passenger-3.0.21-5 was updated to fix a race condition with creating temp directories.

However, it did not take into account umask settings like the previous code did.

I've attached a patch that brings the code in line with the way that it used to work and prevents Passenger services from crashing all over the place.

Reproducible: Always

Comment 1 Jamie Duncan 2013-08-16 20:20:26 UTC
Created attachment 787454 [details]
accounts for umask

Comment 2 Ben Cotton 2020-11-05 16:46:03 UTC
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version.

Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged  change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.

Comment 3 Ben Cotton 2020-11-30 15:15:29 UTC
EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
EPEL please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.