https://bugs.documentfoundation.org/show_bug.cgi?id=147291
--- Comment #14 from Alex Thurgood <ipla...@tuta.io> --- (In reply to Heiko Tietze from comment #13) > Some info on bug 142279. In a nutshell: some certificate manager are > hard-coded and clicking the button is supposed to run these tools. Which > depends on the OS but macOS has not been considered yet. > Which is a very sad state of affairs given that we've been touting digital signatures in our marketing hype since... > Apple's keychain tool probably does not work with GPG / WoT but similarly to > Windows with issued certificates. In that's true the keychain tool is > worthless (see also bug 133941 for the situation on Windows). FWIW, my CertEurope USB eIDAS key relies on a third party app called TKM (Trusted Key Manager) to register the hardware key with the OS. The key isn't automatically registered with Apple Keychain. I would have to export the CER from the TKM app and then import it into the Keychain.app. This type of USB hardware key is used by the bar association of France for filing court documents. It is also one of the allowed hardware signing/authentication/non-repudiation keys used for filing documents with the Unified Patent Court. LibreOffice won't find the cert outside of the Mozilla Firefox profile. For example, if I put a copy of the cert in a folder in my home directory and point LibreOffice manually to that folder, it can't find the key. This means that the CER has to be referenced within the Firefox session by creating a software security device containing the path to the DYLIB and then loading that software security device into the Firefox session. This IMHO is the biggest problem with cert management within LO at the moment, to the extent that it relies on Mozilla profiles (Firefox or Thunderbird) to be called when needed. -- You are receiving this mail because: You are the assignee for the bug.
