On Fri, Dec 8, 2023 at 7:40 AM Yury Tarasievich <yury.tarasiev...@gmail.com> wrote:
> Hi, > > Thanks for answering. What fails in > IMPL_LINK( SvxSecurityTabPage, MacroSecPBHdl, > void*, EMPTYARG ) > is that check: > if ( xD.is() ) > And the xD object is non-null at that. > > Somehow I can't set a breakpoint to that > IMPL_LINK call. Neither variants with > SvxSecurityTabPage:: nor name-mangled version > taken out of object file work. > > I don't have a specific file with macros, it's > my StarBasic macros that are failing to run from > their keyboard shortcuts. Running those from > 'Run macro' works (I changed MacroLevel in my > registry to 0 by xml editor). If called by their > keyboard shortcut, those macros show a msgbox > with 'This document contains macros ...may > contain viruses..'. > > My build options are now without system openssl, > didn't retain the previous set. But IIRC, for > the attempts with system openssl I had these > --with-system-openssl=yes --with-system-curl=yes > > changed in the following options set: > > $ ./configure > '--with-build-version=2023-12-04 22:37 - Linux > x86_64' --enable-verbose --enable-crashdump=yes > --enable-opengl --enable-dbus > --with-package-format=installed > --with-dmake-url= > https://sourceforge.net/projects/oooextras.mirror/files/dmake-4.12.tar.bz2 > --with-epm-url= > https://github.com/jimjag/epm/archive/v5.0.0/epm-5.0.0.tar.gz > --without-junit --without-stlport --disable-kde > --disable-kde4 --disable-randr-link > --disable-gconf --disable-gnome-vfs > --disable-gstreamer --with-ppds > --disable-wiki-publisher --disable-category-b > --disable-saxon --disable-pam --disable-odk > --with-jdk-home=/usr/lib64/java > --with-system-stdlibs --with-system-libs=yes > --with-system-jars=no > --disable-bundled-dictionaries --enable-hyphen > --enable-hunspell --with-fonts > --with-system-python=no --with-system-lucene=no > --with-system-hsqldb=no > --with-system-beanshell=no > --with-system-redland=no --with-system-mythes=no > --with-system-icu=no --with-system-openssl=no > --with-system-curl=no --with-system-libxml=no > --with-system-libxslt=no --with-system-expat=no > --with-system-jpeg=no > > The cause of your problem is "--disable-category-b". With this option, my "Macro Security" button also does nothing. I think it's because NSS is category B, and without it, we don't build xmlsecurity module which is needed for the permissions to work properly. OpenSSL has nothing to do with it. The xmlsecurity module uses only 2 providers at the moment, Microsoft's mscrypt on Windows, and Mozilla's NSS library elsewhere. On Linux, without NSS, it cannot work at all, and isn't even compiled from what I see. We should consider developing an OpenSSL-based xmlsecurity provider which not be category B, and which would fetch certificates from eg. the system certificates on Linux. Damjan
