https://bugs.documentfoundation.org/show_bug.cgi?id=167752
Christian Lohmaier <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://www.libreoffice.org | |/about-us/security/advisori | |es/cve-2025-14714/ --- Comment #15 from Christian Lohmaier <[email protected]> --- Guess I can only repeat what I wrote in comment#5 – it is an deliberate change to respect macOS security architecture, and I don't know a way to solve that problem without undoing that fix. See https://www.libreoffice.org/about-us/security/advisories/cve-2025-14714/ There are workarounds I mentioned: #### call your entry point from a python macro you install as an extension or put into the scripts folder. https://wiki.documentfoundation.org/Documentation/DevGuide/Scripting_Framework#Python_script concrete example: 'vnd.sun.star.script:TableSample.py$createTable?langauge=Python&location=share' will be the createTable macro that will create a writer document and insert a table. ### second option is of course to compile LibreOffice yourself without the launch constraint – then none of the checks apply and it will behave as before ### third option is to do a python runtime you install/provide independent of LibreOffice. you can start LibreOffice with parameters to listen on a socket or pipe and communicate that way, that still will work. https://wiki.documentfoundation.org/Documentation/DevGuide/Professional_UNO#Starting_LibreOffice_in_Listening_Mode ### If anyone has a technical suggestion on how to make it work while respecting the "Transparency, Consent, and Control (TCC) permissions" I'm all ears – but I just don't know a way. -- You are receiving this mail because: You are the assignee for the bug.
