Bug 160743 - libgnomeprint shouldn't use the top level /tmp directory
libgnomeprint shouldn't use the top level /tmp directory
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: libgnomeprint (Show other bugs)
rawhide
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Matthias Clasen
bzcl34nup
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-06-16 20:33 EDT by Ivan Gyurdiev
Modified: 2008-04-04 17:07 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-04-04 17:07:22 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Ivan Gyurdiev 2005-06-16 20:33:12 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4

Description of problem:
libgnomeprint uses the top level /tmp directory to exchange print information.
I am not sure of the exact process of how this happens, but it creates
problems for SELinux strict policy. I know libgnomecups also makes use
of this directory.

The problem is that we are trying to restrict content flow for certain
untrusted applications, such as evolution, for example. We want to control
whether evolution can read content, or write content, and we also
mark content written by evolution as untrusted, and potentially dangerous
(to protect from hostile content from the web).

To accomplish this, we have designated top level /tmp as a "content" location,
and SELinux automatically transitions applications to a particular type
upon creating files there. 

However, the intent is to regulate whether "content" is saved or loaded
by the application - not internal data. Because SElinux has limited
capabilities, we are not able to distinguish which is which, without
adding SELinux code to the application and/or libgnomeprint, which
we want to avoid if possible.

I suggest that libgnomeprint and libgnomecups be changed
to not save print data to the top level tmp directory.
Instead, they should use a private subdirectory, which we
can label for that purpose. I think it is good design practice
to separate internal program data from user-visible content
when possible - this will make SElinux' job a lot easier.

Ivan Gyurdiev @ Red Hat
SELinux Intern

Version-Release number of selected component (if applicable):


How reproducible:
Didn't try


Additional info:
Comment 1 Bug Zapper 2008-04-03 12:12:40 EDT
Based on the date this bug was created, it appears to have been reported
against rawhide during the development of a Fedora release that is no
longer maintained. In order to refocus our efforts as a project we are
flagging all of the open bugs for releases which are no longer
maintained. If this bug remains in NEEDINFO thirty (30) days from now,
we will automatically close it.

If you can reproduce this bug in a maintained Fedora version (7, 8, or
rawhide), please change this bug to the respective version and change
the status to ASSIGNED. (If you're unable to change the bug's version
or status, add a comment to the bug and someone will change it for you.)

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we're following is outlined here:
http://fedoraproject.org/wiki/BugZappers/F9CleanUp

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

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