Bug 436309
Summary: | xguest is preventing firefox from executing openoffice.org | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Daniel Walsh <dwalsh> |
Component: | openoffice.org | Assignee: | Caolan McNamara <caolanm> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | drepper, jnavrati |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-04-08 15:59:31 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
Daniel Walsh
2008-03-06 14:01:37 UTC
We followed http://people.redhat.com/drepper/selinux-mem.html to get ourselves some executable memory so we can make uno work, gcj does the same sort of thing, and probably firefox as well. The locations tried are $HOME followed by /tmp. Which makes it bizarre that it *does* work from the command line and not when firefox spawns off OOo. "xguest user is prevented from executing files in its home directory and /tmp" So, without firefox in the equation is openoffice.org able to launch directly as this xguest user ? I basically don't understand what distinction is made between the ran-by-firefox case and the ran directly case ? I don't see any possibility of removing the need for OOo to get some executable memory as we build vtables on the fly to connect C++ implementations to calls to uno interface slots, trampolining those calls to to the appropriate implementation slots or to proxies that translate to some other language implementation. No with the appropriate booleans set neither the firefox or the run directly would be allowed to execute files in the homedir/or tmpdir. Does openoffice need this no matter what? IE Can most docs be viewed without uno? We currently have openoffice labeled as a java app, to allow it to run java plugins and thus has execmem/execstack privs. It needs uno to do anything at all, OOo is just a bundle of uno components. And I've hacked the uno stuff to follow the double mmap suggestions that ulrich made in his selinux page. Uli you have any ideas? We need to have executable *somewhere*. either in the home dir or a special, user-writable directory. So far I suggested $HOME. If we want to defined something better then let's do it. Here are my options. I need to allow openoffice to execute files in homedir and /tmp. Currently openoffice is defined java_exec_t to allow it to execmem execstack so that it can run java code. I can allow xguest/xgues_mozilla_t/nsplugin_t to transition to xguest_java_t and allow java apps to execute homedir content. Or I can relabel openoffice to some new context openoffice_t which is allowed to executed files in the homedir, and has all the same privs as xguest + execmem +execstack +exec homedir. I am leaning tow (In reply to comment #7) > I need to allow openoffice to execute files in homedir and /tmp. Why "and"? Only one is needed and one can make a good argument for the former. /tmp is much more dangerous. From my side, just like libffi the last time I looked, the patched OOo tries $HOME followed by /tmp so or should work. Personally I'd even prefer a provided library or glibc call or sommat to just "do the right thing" and bump the details out of my app. So where do we stand with this. Is there any action I need to take from my side, or can this issue now be moved out of the OOo component. Current policy will allow openoffice to execute in the homedir. |