https://bugs.documentfoundation.org/show_bug.cgi?id=157480
Aron Budea <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #3 from Aron Budea <[email protected]> --- (In reply to kdub from comment #2) > Information about the first version that caused this bug: > Version: 7.6.1.0.0+ (X86_64) / LibreOffice Community > Build ID: 3326ae0a9902395224ddd95ca3df069ebffe2990 Commit details: https://cgit.freedesktop.org/libreoffice/core/commit/?id=e3d28846c2343072750197fcdeaf44a945ddcb61 author Caolán McNamara <[email protected]> 2023-07-28 12:13:41 +0100 committer Thorsten Behrens <[email protected]> 2023-07-29 02:30:34 +0200 "follow python recommendation and pass SSL contexts" I see a conversation from Thorsten Behrens and Mike Kaganski in the gerrit change that could be relevant. https://gerrit.libreoffice.org/c/core/+/155016 Thorsten: "Some more testing done - not using system python might require setting the path to a system cert store, e.g. for a --enable-python=internal build, this does it for me: SSL_CERT_FILE=/etc/ssl/ca-bundle.pem ./soffice --writer I'm not sure if there's a good way to override --openssldir=<foo> for our internal openssl to make that suck less?" Mike: "We surely have some mechanism to know the used cert store - e.g., for signing documents. Can we re-use it to feed that information to (built-in) Python? Possibly not only to built-in, because I suppose users would expect all components to use a consistent config?" Thorsten: "The problem is the set of different libraries we're using for this. For internal python, we use a shared openssl instance. But in general, yes, getting better at using std OS stuff should be a goal (e.g. I find the certifi python module, spun out of request package, that pops up on SO to solve this for Macs)." -- You are receiving this mail because: You are the assignee for the bug.
