Peter Eberlein wrote: > Hi Mathias, > > Mathias Bauer schrieb: >> Peter Eberlein wrote: >> > >> Macro security is about macro execution, not about availability of the >> BasicIDE. > > And that's the point. You cannot forbid the execution of internal > non-document-bound macros with the security settings.
Yes, that's true. But this also is not related to the availability of the BasicIDE in general. Even if we found an easy way to disable the IDE you still could execute macros from share/basic and user/basic. While we are at it: currently we are thinking about a special configuration setting in OOo that prevents the execution of macros if they are not signed, even if they are not document-bound. I assume that this is what you are talking about. The tricky part of this feature is that then all macros OOo's needs for internal purposes must be signed (that makes our build process much more complicated) and we must provide a tool for admins to sign macros they want to deploy in their installation. The setting and its handling are easy to implement. Ciao, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to "[EMAIL PROTECTED]". I use it for the OOo lists and only rarely read other mails sent to it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
