Bug 21699

Summary: Make it possible to lock down the protocols that mission-control can use
Product: Telepathy Reporter: Vincent Untz <vuntz>
Component: mission-controlAssignee: Telepathy bugs list <telepathy-bugs>
Status: RESOLVED MOVED QA Contact: Telepathy bugs list <telepathy-bugs>
Severity: enhancement    
Priority: low    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments: MC 4.67 lockdown

Description Vincent Untz 2009-05-12 04:04:21 UTC 
Created attachment 25791 [details] [review]
MC 4.67 lockdown

Apparently, there's a demand to add some lockdown to mission-control to limit the protocols users can use. This is mainly a concern if a company needs telepathy-haze for some weird protocol, but doesn't want, say, msn, for example.

I'm attaching a patch that was done for MC 4.67. I didn't review it and I've been told that it'd need a rewrite for MC 5 anyway, but it helps illustrate the thing, I guess.
Comment 1 Simon McVittie 2009-05-13 04:06:31 UTC 
enhancement/low. If we implement this at all (which I'm not sure is appropriate), we should make MC 5 stable first.
Comment 2 GitLab Migration User 2019-12-03 19:33:18 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-mission-control/issues/6.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.