Targetted for 2.7...

see http://www.gnome.org/learn/admin-guide/latest/lockdown-0.html

see bug 346041 for a possible partial implementation example.

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).

I'll work on this.

federico, any news here?

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.

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?

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 :(

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.