Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 196877 - gaim2 needs to be mono_exec_t
gaim2 needs to be mono_exec_t
Product: Fedora
Classification: Fedora
Component: selinux-policy (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Walsh
Depends On:
Blocks: FC6Blocker
  Show dependency treegraph
Reported: 2006-06-27 10:16 EDT by Jeremy Katz
Modified: 2007-11-30 17:11 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-07-17 15:30:27 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 Jeremy Katz 2006-06-27 10:16:46 EDT
With gaim2, there's the possibility of writing plugins in C#.  This then means
that we end up needing to label /usr/bin/gaim as mono_exec_t for execmem permissions

This does scare me a little, though, as given gaim's less than stellar security
record, I'm not 100% sure that we really want to be doing this.  Thoughts?
Comment 1 Warren Togami 2006-06-27 13:13:28 EDT
Adding Bressers, who may have security related opinions on this matter.
Comment 2 Josh Bressers 2006-06-27 13:35:12 EDT
Gaim has had a fairly decent security track record as of late, but this still
worries me.  Could it be possible to have the first packaged plugin that needs
this to set the label?

I imagine most gaim users do not install random plugins, which would make this
change more secuirty risk than feature.
Comment 3 Warren Togami 2006-06-27 13:51:53 EDT
For now Jeremy recommended that we disable mono in our build temporarily until
we decide, or come up with a better solution.
Comment 4 Tom "spot" Callaway 2006-06-27 13:55:51 EDT
I don't care either way, as I disable selinux by default.
Comment 5 Warren Togami 2006-06-29 15:17:03 EDT
Upstream says that mono support is currently very non-functional, so it is
probably a good idea that we have this disabled for now anyway.

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