Hi guys,

I still have my issue with 'Macro Security' button or, rather, with the macro security subsystem not allowing my macros to be run off keyboard shortcuts.

My supposition (maybe wrong) is that the certificates got stale, so I've tried to plug in the newest version of the (possibly) corresponding external dependency, specifically, 'xmlsec1' library used in 'libxmlsec' module (1.3.2 vs 1.2.14 in the trunk). Anyway, wouldn't hurt to have the up-to-date code dealing with security, right?

But I'm getting some errors related to changes in library's API. Should I try to change the code using the related calls (in 'xmlsecurity' component), or maybe someone would take it on oneself? There seem to be like 5-6 instances of deprecated syntax use, so it's not completely overwhelming, but for me that's a significant amount of work, especially considering that's a security-related code.

-Yury

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Reply via email to