https://bugs.documentfoundation.org/show_bug.cgi?id=161872
--- Comment #6 from Miklos Vajna <[email protected]> --- Aha, exciting. :-) So probably this will be a problem in upstream xmlsec, but most likely Aleksey don't want to build libreoffice to debug this, so we should make this as easy for him as possible. It may make sense to file an issue at https://github.com/lsh123/xmlsec/ and point to this bug. If signing fails, we should emit warnings in the dbgutil case on stderr. Could you please check: 1) In XMLSignature_NssImpl::generate(), when we do the xmlSecDSigCtxSign() call that is the actual signing, do you get an error? 2) If you get an error, then ideally we get error details via the xmlsec log callback, can you check if errorCallback() gets called? If so, do we get any details there, why the signing fails? 3) Last idea: we have this own code at verifyCertificate(), there we emit lots of SAL_INFOs, can you check that finds no errors? Thanks. FWIW I'm on openSUSE Leap 15.5, I guess there is some openSUSE vs Debian difference here that makes signing work here, but not there. -- You are receiving this mail because: You are the assignee for the bug.
