Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 196877

Summary: gaim2 needs to be mono_exec_t
Product: [Fedora] Fedora Reporter: Jeremy Katz <katzj>
Component: selinux-policyAssignee: Daniel Walsh <dwalsh>
Status: CLOSED DEFERRED QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: bressers, dwalsh, stu, tcallawa, wtogami
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: 2006-07-17 19:30:27 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:
Bug Depends On:    
Bug Blocks: 150224    

Description Jeremy Katz 2006-06-27 14:16:46 UTC
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 17:13:28 UTC
Adding Bressers, who may have security related opinions on this matter.

Comment 2 Josh Bressers 2006-06-27 17:35:12 UTC
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 17:51:53 UTC
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 17:55:51 UTC
I don't care either way, as I disable selinux by default.

Comment 5 Warren Togami 2006-06-29 19:17:03 UTC
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.