Red Hat Bugzilla – Full Text Bug Listing
|Summary:||Propose that you turn on PrivateTmp=true in service file for cyphesis|
|Product:||[Fedora] Fedora||Reporter:||Daniel Walsh <dwalsh>|
|Component:||cyphesis||Assignee:||Martin Preisler <mpreisle>|
|Status:||NEW ---||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||rawhide||CC:||atorkhov, bruno, mpreisle|
|Fixed In Version:||Doc Type:||Enhancement|
|Doc Text:||Story Points:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Bug Depends On:|
Description Daniel Walsh 2012-01-17 10:36:08 EST
I would like to propose using PrivateTmp for cyphesis, to make it more secure and avoid users from being able to potentially effect it. http://fedoraproject.org/wiki/Features/ServicesPrivateTmp
Comment 1 Daniel Walsh 2012-02-06 15:45:53 EST
Any change on this bug. We are coming up to Feature Freeze, and would like some comment on this bug. If you do not believe this application uses /tmp than please comment on this and close the bug. If you believe this application needs to use /tmp to communicate with other applications or users then you can close this bug with that comment. If your app does not use systemd, then close this bug with that comment. If you have no idea, then please add a comment, and change the bug to assigned. I need to update the status on this feature. Thanks for your help.
Comment 2 Bruno Wolff III 2012-02-06 16:07:00 EST
Cyphesis is not currently using systemd and I won't get to it before alpha (and I don't think the other maintainer will either). Not many people are going to be running the server (as compared to using the ember client) so I haven't been treating this as high priority and have been mostly working on FTBFS issues. Assuming we are allowed to change this between alpha and beta, I might be able to get to it before beta.
Comment 3 Daniel Walsh 2012-02-06 16:31:04 EST
Ok Thanks for updating the info.
Comment 4 Fedora End Of Life 2013-04-03 12:24:47 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
Comment 5 Fedora End Of Life 2015-01-09 11:57:12 EST
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.