I have a few macros that run or are available for everything. I'd like to sign them and trust my signature so that I don't have to allow macros every time I open a document. These macros are saved in My Macros & Dialogs > Standard > Module1. I can sign spreadsheets, and my signature is trusted, but the BASIC IDE does nothing when I click on File > Digital Signatures... I expect a dialog to appear inviting me to select a signature. I don't have much interest in simply trusting their location, because everything I do can write there. Version: 7.2.3.2 / LibreOffice Community Build ID: 20(Build:2) Locale: en-GB (en_GB.UTF-8); UI: en-GB Ubuntu package version: 1:7.2.3-0ubuntu0.21.10.1 Calc: threaded
Hello, se help: https://help.libreoffice.org/7.2/en-US/text/shared/guide/digitalsign_send.html
Created attachment 177214 [details] signed macro security warning
From the tools > macro menu I do have access to digitally sign the macros in the document. After the macro is signed, when I open the IDE, the file > digital signatures... option opens the signature dialog as expected. When opening the document the "security warning" dialog appears telling me the macros are signed by: <blank>. See attachment. Clicking on the view signatures button causes LO to hang until it is killed. Selecting "always trust macros from this source..." seems to do nothing. Other Information: Something seems to have broken for me recently. When I look at Tools > Options > LibreOffice > Security > Macro Security... I have a large error dialog titled "Macro security problem!" The content starts with "Broken certificate data: mQIN..." and ends with "Vs= / com.sun.star.uno.RuntimeException message: ./xmlsecurity/source/xmlsec/nss/x590certificate_nssimpl.cxx:326" Copy & paste wasn't available so I had to type that... please excuse mistakes.
gah! ./xmlsecurity/source/xmlsec/nss/x509certificate_nssimpl.cxx
Please clarify: signing only works with x509 certificates kindly confirm if x509 certificates were used. more info: https://bugs.documentfoundation.org/show_bug.cgi?id=115884 Hello, Thank you for reporting the bug. Can you please confirm if the issue still exists in the latest build? Could you please try to reproduce it with a master build from https://dev-builds.libreoffice.org/daily/master/ ? You can install it alongside the standard version. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the master build.
Dear documentfoundation@pelly.co, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear documentfoundation@pelly.co, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp