https://bugs.documentfoundation.org/show_bug.cgi?id=161872
--- Comment #15 from Moritz Duge (allotropia) (a.k.a. kolAflash) <[email protected]> --- (In reply to alex.ilmar4spam from comment #13) > (In reply to Moritz Duge (allotropia) (a.k.a. kolAflash) from comment #12) > > [...] > > On Windows the X.509 ODF signing may be completely broken... > [...] > Is there a need to create a separate bug-report? What other useful > information can I provide? If you have some spare time, you may try to find the exact commit which broke the behavior on Windows. LibreOffice has a repositories of binary builds to conduct such tests. It's called Bibisect. (binary bisect) https://wiki.documentfoundation.org/QA/Bibisect Use Git to clone the LibreOffice-24.2 for Window Bibisect repo. https://bibisect.libreoffice.org/win64-24.2 First test the binary commit based on the bad commit bfd479abf I found. Just grep for it in the Git log. The test the previous binary commit git log | grep -C10 bfd479abf If that's not the bad commit, you may do a full bisect testing. https://en.wikipedia.org/wiki/Bisection_(software_engineering) If Windows is also broken by commit bfd479abf then I'd say we handle it in this ticket. If another commit is the bad commit, you may open a new ticket. Thanks! (In reply to Miklos Vajna from comment #14) > [...] nobody filed > an libxmlsec upstream issue to ask the maintainer if this is intentional or > not. You can do that at https://github.com/lsh123/xmlsec/ I just filed an upstream issue. https://github.com/lsh123/xmlsec/issues/866 I'm just guessing, that you have far better insight than I do to drive the upstream issue forward. -- You are receiving this mail because: You are the assignee for the bug.
