Issue 90822 - SESELinux 'execheap' violation at startup
Summary: SESELinux 'execheap' violation at startup
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 2.4.1
Hardware: PC Linux, all
: P2 Trivial (vote)
Target Milestone: ---
Assignee: michael.ruess
QA Contact: issues@sw
URL:
Keywords: needmoreinfo, oooqa
Depends on:
Blocks:
 
Reported: 2008-06-17 20:14 UTC by jimavera
Modified: 2008-12-16 17:09 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Detailed error report from SELinux (2.52 KB, text/plain)
2008-06-17 20:15 UTC, jimavera 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description jimavera 2008-06-17 20:14:40 UTC 
OO2.4.1, after being installed via an update from 2.4,
aborts immediately on Fedora Core 7 (and most likely later versions)
because of an SELinux 'execheap' violation.   

I will attach the complete error report from SELinux.   But in essence it
says the program contains incorrect code which is a security risk.

The SELinux web site discusses how to write code which avoids this problem
(it says to use mmap to allocate anonymous storage for generated code,
not malloc + mprotect)

Please see the 'execheap' section of
http://people.redhat.com/drepper/selinux-mem.html
Comment 1 jimavera 2008-06-17 20:15:39 UTC 
Created attachment 54549 [details]
Detailed error report from SELinux
Comment 2 eric.savary 2008-06-18 10:31:15 UTC 
I guess this happens with any other apps (Calc, Impress...)?
Are you sure this affects 2.4.0 -> 2.4.1?
The error report shows: openoffice.org-writer-*2.2.1*-18.2.fc7
Comment 3 michael.ruess 2008-07-04 13:40:46 UTC 
I cannot reproduce this problem. Tested it with native OO 2.4.1 and 3.0 dev
build on WinXP, Fedora Core and SUSE 10.2. You are running Fedora using the
by-packed OOo build. Please refer to the distributors support or even run the
native OOo builds which can be downloaded from Openoffice.org.
Comment 4 michael.ruess 2008-07-04 13:41:44 UTC 
Closed.
Comment 5 caolanm 2008-12-16 17:09:29 UTC 
FWIW a lot of those execheap errors that claim to be from e.g. openoffice.org
are in fact from e.g. nvidia or some other driver that has a replacement libGL
and so apps that use opengl fail. To make OOo not try and use libGL then 
export SAL_NOOPENGL=true
is a workaround, i.e. if export SAL_NOOPENGL=true makes it work, then the
problem is not that of OpenOffice.org, but that of a bad libGL.so.1