After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 335923 - Lockdown support meta-bug
Lockdown support meta-bug
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: general
2.6.x (obsolete)
Other Linux
: High major
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
evolution[kill-bonobo]
Depends on: 322553 335891 335892 335895 335896
Blocks:
 
 
Reported: 2006-03-25 03:58 UTC by Karsten Bräckelmann
Modified: 2013-09-10 14:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Karsten Bräckelmann 2006-03-25 03:58:48 UTC
This bug is meant to track implementation of proper lockdown support
(Pessulus, Sabayon).
Comment 1 Karsten Bräckelmann 2006-03-25 13:22:58 UTC
Targetted for 2.7...
Comment 3 André Klapper 2006-07-28 18:48:56 UTC
see bug 346041 for a possible partial implementation example.
Comment 4 André Klapper 2006-08-22 22:26:09 UTC
2.9. major issue.
gnome targets deployments, so behave like that.
http://primates.ximian.com/~federico/docs/2006-GUADEC/how-much-faster/img27.html

so find the UI places where lockdown needs to be supported and fix it (please use harmonized error strings here).
Comment 5 Federico Mena Quintero 2007-02-13 00:59:50 UTC
I'll work on this.
Comment 6 André Klapper 2007-07-31 09:36:44 UTC
federico, any news here?
Comment 7 Federico Mena Quintero 2007-07-31 15:30:19 UTC
Ugh, it seems that the Evo people and I never managed to have lunch together to talk during GUADEC :)  I'll start the discussion on the mailing list.
Comment 8 Matthew Barnes 2009-08-25 15:53:38 UTC
I added support for some lockdown features on the kill-bonobo branch.

We at least have EShell hooks for everything listed in GConf under /desktop/gnome/lockdown.  Is there more?
Comment 9 Federico Mena Quintero 2009-08-25 18:04:16 UTC
The hardest feature for Evo is probably "disable command line", which actually means "don't let the user specify by hand any programs to run".  Evolution can let you "subvert" that in several ways... defining programs to run when a calendar alarm triggers, and some others which I forget right now.

I'd rather close this bug, or re-purpose it as a tracker bug for particular lockdown bugs as they are discovered --- this bug is too abstract, unfortunately :(
Comment 10 Matthew Barnes 2009-08-25 18:27:01 UTC
I agree with closing this.  I'd rather track individual lockdown issues with a whiteboard tag or Bugzilla keyword.

Currently I have full lockdown support for printing, and the signature script feature is disabled for "disable command line", but not yet for alarms, filters, and wherever else it's needed.  No support yet for "disable application handlers" and "disable save to disk" (that one's likely to be fraught with loop holes even if we do disable save dialogs).

Closing as obsolete.