Bug 446610 - SELinux complains about memory allocation
SELinux complains about memory allocation
Product: Fedora
Classification: Fedora
Component: openoffice.org (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Caolan McNamara
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-05-15 07:22 EDT by Simon Fonceca
Modified: 2008-05-15 08:12 EDT (History)
1 user (show)

See Also:
Fixed In Version: F-9
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-15 08:12:57 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Simon Fonceca 2008-05-15 07:22:29 EDT
Description of problem:
SELinux doesn't like memory allocation in openoffice

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

How reproducible:

Steps to Reproduce:
1. Install openoffice-writer + subdependencies
2. run Writer
Actual results:
SeLinux output 
SELinux is preventing /usr/lib/openoffice.org/program/swriter.bin from changing
the access protection of memory on the heap.
Detailed Description
The /usr/lib/openoffice.org/program/swriter.bin application attempted to change
the access protection of memory on the heap (e,g., allocated using malloc). This
is a potential security problem. Applications should not be doing this.
Applications are sometimes coded incorrectly and request this permission. The
SELinux Memory Protection Tests web page explains how to remove this
requirement. If /usr/lib/openoffice.org/program/swriter.bin does not work and
you need it to work, you can configure SELinux temporarily to allow this access
until the application is fixed. Please file a bug report against this package.

Expected results:

Additional info:
Comment 1 Caolan McNamara 2008-05-15 08:12:57 EDT
Fedora 7 is basically at the end of life. Everything should be ok in F8 and F9
wrt selinux. And IIRC so was 7 actually. Quite possibly you have e.g. a third
party video driver which doesn't work with selinux and writer (due to querying
for opengl data) gets the blame

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