[Libreoffice-bugs] [Bug 126409] Notarize LibreOffice builds so that it launches without warnings on macOS 10.15 Catalina
https://bugs.documentfoundation.org/show_bug.cgi?id=126409 Telesto changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||4595 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126409] Notarize LibreOffice builds so that it launches without warnings on macOS 10.15 Catalina
https://bugs.documentfoundation.org/show_bug.cgi?id=126409 Christian Lohmaier changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #56 from Christian Lohmaier --- (In reply to Tor Lillqvist from comment #55) > But the LibreOffice.app one downloads from TDF is still not notarized, is > it? No - all mac builds for 6.3 and later versions you can download from www.libreoffice.org are notarized. Daily builds created by tinderboxes are not signed at all and therefore also not notarized. > So in what way could this bug be seen as resolved? The question is: why is this still open. And the answer is: mixing of different stuff. Problem initially was with Gatekeeper in macOS Catalina. A bug in Catalina's gatekeeper. That still claimed that it was not notarized despite having been notarized and the commandline tools (spctl, codesign, stapler) all confirming that. If you get the message "has been checked by Apple for malware" when opening (and are able to launch it without going to system settings and set a security exception or using alt-open to add the exception that way): that is the end-user visible proof of successful notarization. Confirmed by multiple persons that gatekeeper in current version of Catalina no longer (falsely) accuses the App of not being notarized → resolving WFM. As for stapling the info the dmg and not the app included in the dmg container: also expected/as designed: https://github.com/akeru-inc/xcnotary/issues/3#issuecomment-622022976 > Our general advice here is that you sign everything, from the inside out, and > > then notarise and staple the outermost container. That ticket covers all > the > code included in the container. When Gatekeeper checks the code > signature of > the container, it will ingest the ticket, avoiding the need > for a round trip > to the notary service on first run. As to .app folder being modified post-gatekeepr/notarization checks: Those already have corresponding separate bugs, but those are unrelated to gatekeeper and notarization. That's only checked on first launch. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126409] Notarize LibreOffice builds so that it launches without warnings on macOS 10.15 Catalina
https://bugs.documentfoundation.org/show_bug.cgi?id=126409 --- Comment #55 from Tor Lillqvist --- But the LibreOffice.app one downloads from TDF is still not notarized, is it? So in what way could this bug be seen as resolved? Even if it apparently now is still possible, after all, to run non-notarized (only signed) 3rd-party software downloaded from random sites, isn't the point that this might change at some point and it would be good to be prepared for that, and not desperately then try to fix it when the problem materializes for real? It shouldn't be hard to understand that Apple wants to continuouslu increase the security of macOS. As such, personally, I much prefer the App Store as a distribution channel for macOS software. LibreOffice Vanilla has been available there for several years. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126409] Notarize LibreOffice builds so that it launches without warnings on macOS 10.15 Catalina
https://bugs.documentfoundation.org/show_bug.cgi?id=126409 --- Comment #54 from MattJ --- I installed 6.4.4.2 on the same system I had problem with before. This time it started with the expected warning that the application was downloaded from the internet. Once I clicked OK on that dialog LO opened with no problem. I did not get any warnings about Apple not being able to verify it. This works for me now. I think it can be closed. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126409] Notarize LibreOffice builds so that it launches without warnings on macOS 10.15 Catalina
https://bugs.documentfoundation.org/show_bug.cgi?id=126409 --- Comment #53 from eisa01 --- (In reply to Christian Lohmaier from comment #50) > Creation of compiled py files (pyc) is also something that only happens > after LO was launched. So similar to the languagepack installation it is a > post-gatekeeper modification of the .app bundle. Not nice, for sure, but > unrelated to gatekeeper/notarization when doing the first-launch > verification by macOS Ah, ok > > a .app copied from the dmg to your local disk before launching it should > verify: Yup, I can also see that now > (and launching it for the first time should show the dialog with the > "..downloaded from... checked by apple for malware and none was found" > dialog.) > > After having launched LO (or more specifically: doing something that > triggers initialization of python, i.e. opening/creating a writer document → > some writing aids use python → python creates it pyc files) I can confirm > the python files messing up the integrity on disk, but as said: that is > after LO was already green-lit by gatekeeper. But I guess we have no guarantee that it doesn't cause problems (e.g., the mysterious save-as issues) At least after those python files are created, macOS doesn't treat the .app as notarised any more if it does a recheck. Who knows when that happens, or if the behaviour will change in a future system update > # stapling ### > as for stapling: In LO's case: the thing you download is stapled, not just > the contents, so the dmg has the notarization-staple-info for the app > assigned to it. > > ### > > Opening the app for the first time does not show a "verify" progress bar as > > LO does, > > likely because the Firefox app is too small/the scanning is fast enough to > not make it trigger a dialog for that. If you mean verify progress when > opening the dmg: that happens for firefox as well/any dmg, but that is just > checksum based verification of the dmg for download errors. Ah, true. Thanks for explaining all of this! So in a nutshell: LO is notarised on first launch, but as soon as you do something the .app bundle is corrupted and the .app is no longer notarised So technically WFM, but I'm not sure there's any point in creating a new bug "Notarisation corrupted" of "highest/critical" rating and readding everyone to CC from this bug? -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126409] Notarize LibreOffice builds so that it launches without warnings on macOS 10.15 Catalina
https://bugs.documentfoundation.org/show_bug.cgi?id=126409 --- Comment #52 from Tor Lillqvist --- steve, so are you saying that this bug, that LibreOffice builds should be notarized, is invalid, as it works for you anyway? Interesting. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126409] Notarize LibreOffice builds so that it launches without warnings on macOS 10.15 Catalina
https://bugs.documentfoundation.org/show_bug.cgi?id=126409 --- Comment #51 from steve -_- --- Tested LO 6.4.4 on macOS 10.15.4 and all checks were fine. No problem after re-installing 6.4.4 to open on macOS. The expected dialog to visit website (from which download was made) or cancle or open app was shown and LO opened fine on first attempt. Considering the findings above I claim this bug here is worksforme. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126409] Notarize LibreOffice builds so that it launches without warnings on macOS 10.15 Catalina
https://bugs.documentfoundation.org/show_bug.cgi?id=126409 --- Comment #50 from Christian Lohmaier --- (In reply to eisa01 from comment #49) > Created attachment 161186 [details] > Failed code sign due to Python framework Creation of compiled py files (pyc) is also something that only happens after LO was launched. So similar to the languagepack installation it is a post-gatekeeper modification of the .app bundle. Not nice, for sure, but unrelated to gatekeeper/notarization when doing the first-launch verification by macOS a .app copied from the dmg to your local disk before launching it should verify: cloph@Catalina-Mac-mini Desktop % spctl -vvv --assess --type exec LibreOffice.app/ LibreOffice.app/: accepted source=Notarized Developer ID origin=Developer ID Application: The Document Foundation (7P5S3ZLCN7) cloph@Catalina-Mac-mini Desktop % codesign --verify --deep --verbose LibreOffice.app/ LibreOffice.app/: valid on disk LibreOffice.app/: satisfies its Designated Requirement cloph@Catalina-Mac-mini Desktop % (and launching it for the first time should show the dialog with the "..downloaded from... checked by apple for malware and none was found" dialog.) After having launched LO (or more specifically: doing something that triggers initialization of python, i.e. opening/creating a writer document → some writing aids use python → python creates it pyc files) I can confirm the python files messing up the integrity on disk, but as said: that is after LO was already green-lit by gatekeeper. # stapling ### as for stapling: In LO's case: the thing you download is stapled, not just the contents, so the dmg has the notarization-staple-info for the app assigned to it. ### > Opening the app for the first time does not show a "verify" progress bar as > LO does, likely because the Firefox app is too small/the scanning is fast enough to not make it trigger a dialog for that. If you mean verify progress when opening the dmg: that happens for firefox as well/any dmg, but that is just checksum based verification of the dmg for download errors. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126409] Notarize LibreOffice builds so that it launches without warnings on macOS 10.15 Catalina
https://bugs.documentfoundation.org/show_bug.cgi?id=126409 --- Comment #49 from eisa01 --- Created attachment 161186 --> https://bugs.documentfoundation.org/attachment.cgi?id=161186=edit Failed code sign due to Python framework The code-signing shows non-clean results on a fresh install (no language pack), no ticket is stapled, and the command line tool does not report LO as notarised >spctl -vvv --assess --type exec LibreOffice.app/ >LibreOffice.app/: a sealed resource is missing or invalid See attachment for full output >codesign --verify --deep --verbose LibreOffice.app/ >LibreOffice.app/: a sealed resource is missing or invalid In subcomponent: This is a regression from when you tested this autumn in comment #24 I haven't opened a new bug about that as the issues are a bit related, or? As per comment #41 passing -vvv is a requirement for notarisation: _The strict flag increases the restrictiveness of the validation to match that required by notarization._ Also, LO should possibly have the ticket stapled to it: >> a degraded user experience, as the first time a user runs a new executable, >>Apple delays execution while waiting for a reply from their server. >The way to avoid this behavior is to staple the notarization ticket to your >bundle (or dmg/pkg), i.e. "/usr/bin/stapler staple ." >Otherwise, Gatekeeper will fetch the ticket and staple it for the user >on the first run. >I'm the author of xcnotary [1], a tool to make notarization way less >painful, including uploading to Apple/polling for >completion/stapling/troubleshooting various code signing issues.) >[1] https://github.com/akeru-inc/xcnotary https://news.ycombinator.com/item?id=23273396 >stapler validate LibreOffice.app/ >Processing: /Applications/LibreOffice.app >LibreOffice.app does not have a ticket stapled to it. For some reason there's no ticket stapled after first run either, which indicates it's not fully compliant given what the author of the xcnotary tool says? --- Checking another popular open source app, Firefox, seems to have everything working in contrast to LO. Opening the app for the first time does not show a "verify" progress bar as LO does, and all the required steps above are satisified (all of these fail on LO) >stapler validate Firefox.app/ >Processing: /Applications/Firefox.app >The validate action worked! >spctl -vvv --assess --type exec Firefox.app/ >Firefox.app/: accepted >source=Notarized Developer ID >origin=Developer ID Application: Mozilla Corporation (43AQ936H96) >codesign --verify --deep --verbose Firefox.app/ >Firefox.app/: valid on disk >Firefox.app/: satisfies its Designated Requirement -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126409] Notarize LibreOffice builds so that it launches without warnings on macOS 10.15 Catalina
https://bugs.documentfoundation.org/show_bug.cgi?id=126409 --- Comment #48 from Christian Lohmaier --- Created attachment 161165 --> https://bugs.documentfoundation.org/attachment.cgi?id=161165=edit no problem with notarization on my fresh Catalina... can anyone actually reproduce the Gatekeeper issue/not showing notarization with a current version of Catalina and current version of LibreOffice? Messing with the .app directory comes after gatekeeper, so checking signatures after installing languagepack is expected to not show clean result. I could reproduce it when Catalina first came out, but not with a clean installation I did today (no build-environment or other stuff installed) "Apple hat sie auf Malware überprüft und keine gefunden" → the string you get when it was successfully notarized (Apple checked it for malware and couldn't find any) -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126409] Notarize LibreOffice builds so that it launches without warnings on macOS 10.15 Catalina
https://bugs.documentfoundation.org/show_bug.cgi?id=126409 Telesto changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||8549 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126409] Notarize LibreOffice builds so that it launches without warnings on macOS 10.15 Catalina
https://bugs.documentfoundation.org/show_bug.cgi?id=126409 --- Comment #47 from Tor Lillqvist --- I wrote: > No, I am not volunteering to fix this But I did not have to volunteer, I am now in the progress of fixing it as part of my job. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126409] Notarize LibreOffice builds so that it launches without warnings on macOS 10.15 Catalina
https://bugs.documentfoundation.org/show_bug.cgi?id=126409 --- Comment #46 from eisa01 --- I really don't know anything about this at all, but saw a reference to a helper app for notarizing that may help solve this? https://github.com/akeru-inc/xcnotary >From this comment chain: https://news.ycombinator.com/item?id=23086538 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126409] Notarize LibreOffice builds so that it launches without warnings on macOS 10.15 Catalina
https://bugs.documentfoundation.org/show_bug.cgi?id=126409 --- Comment #45 from Tor Lillqvist --- I see Python mentioned. If the problem is that Python writes bytecode files into the app bundle, would 4e124fd1409af419990bacade74fcf355624243f help? Are the notarized builds configured with --enable-readonly-installset? -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126409] Notarize LibreOffice builds so that it launches without warnings on macOS 10.15 Catalina
https://bugs.documentfoundation.org/show_bug.cgi?id=126409 --- Comment #44 from Tor Lillqvist --- > Langpack installer installs additional files to the app directory That is and has always been a HORRIBLE idea. The intent has always been, I assume, that an app bundle should be read-only, even if it has not been enforced. Installing a separate langpacks should put it into ~/Library for instance. (No, I am not volunteering to fix this. I work on the App Store build, which comes with a set of bundled langpacks.) -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126409] Notarize LibreOffice builds so that it launches without warnings on macOS 10.15 Catalina
https://bugs.documentfoundation.org/show_bug.cgi?id=126409 eisa01 changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||2025 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126409] Notarize LibreOffice builds so that it launches without warnings on macOS 10.15 Catalina
https://bugs.documentfoundation.org/show_bug.cgi?id=126409 eisa01 changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||6638 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126409] Notarize LibreOffice builds so that it launches without warnings on macOS 10.15 Catalina
https://bugs.documentfoundation.org/show_bug.cgi?id=126409 eisa01 changed: What|Removed |Added Blocks||128233 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=128233 [Bug 128233] macOS: Can't save or open files using Finder dialog on Standard accounts on macOS 10.15 Catalina -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126409] Notarize LibreOffice builds so that it launches without warnings on macOS 10.15 Catalina
https://bugs.documentfoundation.org/show_bug.cgi?id=126409 --- Comment #43 from mimaj...@163.com --- The same issue still reproducible on Libreoffice 6.4.2.2: $ cat LibreOffice.app/Contents/Info.plist | grep -i "LibreOffice 6" LibreOffice 6.4.2.2 $ /Applications stapler validate LibreOffice.app Processing: /Applications/LibreOffice.app LibreOffice.app does not have a ticket stapled to it. $ codesign -vvv --deep --strict LibreOffice.app ... LibreOffice.app: a sealed resource is missing or invalid In subcomponent: /Applications/LibreOffice.app/Contents/Frameworks/LibreOfficePython.framework ... -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126409] Notarize LibreOffice builds so that it launches without warnings on macOS 10.15 Catalina
https://bugs.documentfoundation.org/show_bug.cgi?id=126409 Julien Nabet changed: What|Removed |Added Severity|major |critical Priority|high|highest --- Comment #42 from Julien Nabet --- Ok there's no crash, it's MacOs specific and some may consider it's not a regression because it's due to new policy from Apple but, considering all the comments, it seems a blocker on MacOs Catalina and future MacOS versions. Let's put the max priority unless being compatible with MacOS is just a bonus feature. If someone wants to revert this, please explain why. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126409] Notarize LibreOffice builds so that it launches without warnings on macOS 10.15 Catalina
https://bugs.documentfoundation.org/show_bug.cgi?id=126409 --- Comment #41 from eisa01 --- The Python issue is definitely holding up the notarization, this was not an issue in comment #24, so we've actually regressed on achieving a proper notarization :) Use the vvv flag to perform a verification with elevated verbosity. You use the deep flag to ensure the utility checks nested code content. _The strict flag increases the restrictiveness of the validation to match that required by notarization._ See the codesign man page for more information about these flags and how to interpret the output. Version: 6.4.1.2 Build ID: 4d224e95b98b138af42a64d84056446d09082932 CPU threads: 4; OS: Mac OS X 10.14.6; UI render: default; VCL: osx; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126409] Notarize LibreOffice builds so that it launches without warnings on macOS 10.15 Catalina
https://bugs.documentfoundation.org/show_bug.cgi?id=126409 --- Comment #40 from eisa01 --- cloph: Are we doing all the required steps? Current instructions say you need to staple the ticket to the binary On 6.4.1.2 the output I get is: stapler validate LibreOffice.app/ Processing: /Applications/LibreOffice.app LibreOffice.app does not have a ticket stapled to it. So either we don't do the step, or something breaks (although it says this is only needed for offline validation, but I' Also there's an issue with the embedded python: >codesign -vvv --deep --strict LibreOffice.app/ >LibreOffice.app/: a sealed resource is missing or invalid >In subcomponent: >>/Applications/LibreOffice.app/Contents/Frameworks/LibreOfficePython.framework So that may be what it complains about: >spctl -vvv --assess --type exec LibreOffice.app/ >LibreOffice.app/: a sealed resource is missing or invalid Notarizing macOS software: https://developer.apple.com/documentation/xcode/notarizing_macos_software_before_distribution Customizing the notarization workflow: https://developer.apple.com/documentation/xcode/notarizing_macos_software_before_distribution/customizing_the_notarization_workflow Resolving common issues: https://developer.apple.com/documentation/xcode/notarizing_macos_software_before_distribution/resolving_common_notarization_issues >If you use an automated build system, you can integrate the notarization >process into your existing build scripts. >The altool and stapler command-line tools (included with Xcode) allow you to >upload your software to the Apple notary service, >and to staple the resulting ticket to your executable. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126409] Notarize LibreOffice builds so that it launches without warnings on macOS 10.15 Catalina
https://bugs.documentfoundation.org/show_bug.cgi?id=126409 --- Comment #39 from mimaj...@163.com --- So what is the plan for this bug now? Is there a plan to fix it or do we have to go and get LibreOffice Vanilla from the Mac AppStore: https://apps.apple.com/cn/app/libreoffice-vanilla/id921923693?l=en=12 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126409] Notarize LibreOffice builds so that it launches without warnings on macOS 10.15 Catalina
https://bugs.documentfoundation.org/show_bug.cgi?id=126409 steve -_- changed: What|Removed |Added Version|6.3.1.2 release |Inherited From OOo -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126409] Notarize LibreOffice builds so that it launches without warnings on macOS 10.15 Catalina
https://bugs.documentfoundation.org/show_bug.cgi?id=126409 steve -_- changed: What|Removed |Added URL||https://developer.apple.com ||/documentation/xcode/notari ||zing_macos_software_before_ ||distribution -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126409] Notarize LibreOffice builds so that it launches without warnings on macOS 10.15 Catalina
https://bugs.documentfoundation.org/show_bug.cgi?id=126409 steve -_- changed: What|Removed |Added Summary|LibreOffice does not launch |Notarize LibreOffice builds |normally on macOS 10.15 |so that it launches without |Catalina|warnings on macOS 10.15 ||Catalina -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
