MacOS signing issue.
Michael Reeves
reeves.87 at gmail.com
Thu Oct 22 22:12:18 BST 2020
Thanks. I will be updating and closing the issue since I have no control
over any of this.
On Thu, Oct 22, 2020, 1:15 PM Jeremy Whiting <jpwhiting at kde.org> wrote:
> Notarizing and signing are actually separate things on MacOS, signing the
> app or checking the signature of the dmg are orthogonal to the issue
> described and the popup in that report. Notarization is sending the app
> (zipped) to apple's notarization service so they can check it doesn't use
> any apis that it shouldn't or something, then the .app needs to be
> "stapled" with the notarization before putting it into the dmg. That said
> iirc signing the app is a requirement before submitting the app to apple's
> notarization service in the first place.
>
> On Thu, Oct 22, 2020 at 11:12 AM Ben Cooksley <bcooksley at kde.org> wrote:
>
>> On Fri, Oct 23, 2020 at 6:08 AM Michael Reeves <reeves.87 at gmail.com>
>> wrote:
>>
>>> Could someone familiar with the CI and OS X signing machinism look at
>>> this.
>>>
>>> https://bugs.kde.org/show_bug.cgi?id=428062
>>>
>>> I have no way to test or fix this issue. Which as far as I know is an
>>> issue with the CI on binary factory.
>>>
>>
>> This is because Craft to my knowledge at this time does not support
>> notarization of MacOS binaries.
>>
>> Once that has been added, the issue should disappear.
>>
>> Regards,
>> Ben
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-devel/attachments/20201022/771f116e/attachment.htm>
More information about the kde-devel
mailing list