GNOME Bugzilla – Bug 605280
Beginnings of a patch for OpenOffice.org lockdown
Last modified: 2013-01-15 22:43:29 UTC
Created attachment 150271 [details] [review] Patch to (badly) add OpenOffice.org support into the pessulus ui Hi, Vincent and Rob. Here's the makings of an updated patch for an old patch we had in sabayon for doing OpenOffice.org lockdown. Federico asked if I could forward this to you. I've done a half-arsed job of converting the UI, quite frankly, I'm amazed this works at all, but it does bring up the OO.o ui, albeit to the right of everything else, in the old top-tab style. I'm a plumbing guy, so I haven't a hot clue how to fix it from here, however, all the python goodies I've ported across. If you can fix up the UI, I'll look into updating the string types for the OOo part (you want to save in ODT now, not sxw, etc) and I'll even put some effort into writing a section for the pessulus help file for it. Let me know! Cheers, Scott
I'm cross-linking sabayon bug #320592 to this.
One issue here is that a lot of settings you're adding are not related to lockdown. I don't think they should be added in pessulus, but if they're useful, they belong to an application like the yet-to-be-written GNOME Plumbing. Also some of the lockdown settings in OOo are surprising. I don't see the point of locking down something like "Recommend password on save", for example. It could make sense if it was "Require" instead of Recommend. Do we have any way to influence how OOo deals with lockdown?
Scott: also, Michael told me that he's not sure those gconf keys are still valid. Can you double-check?
We are sorry, but pessulus will no longer be maintained due to lack of manpower. I am closing all remaining open bug reports. Pessulus is already closed down for new report submissions. Apologies for the noise and any inconvenience caused by it.