Bug 761257

Summary: Avoid using /tmp in Pulp plugins
Product: [Community] PulpDist Reporter: Nick Coghlan <ncoghlan>
Component: Pulp PluginsAssignee: Nick Coghlan <ncoghlan>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: medium    
Version: unspecified   
Target Milestone: 0.1.0   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 761253 Environment:
Last Closed: 2011-12-12 07:36:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Nick Coghlan 2011-12-07 22:20:24 UTC 
Using /tmp for any kind of operations in a service can cause SELinux compatibility problems and open up genuine security holes (see http://danwalsh.livejournal.com/11467.html)

pulpdist.core.sync_trees should be updated to accept a configurable temp dir, then the Pulp plugins updated to use the conduit's working directory API to get an appropriate path.
Comment 1 Nick Coghlan 2011-12-12 07:36:06 UTC 
Simpler solution: log data isn't stored on the filesystem while a job is in progress. Instead, it is held in RAM, and passed to Pulp for storage when the job completes (regardless of success or failure).

(feedback will also be passed upstream about the desirability of a better mechanism for recording partial log data in the event of failures)