[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: MacOS signing issue.
From:       Jeremy Whiting <jpwhiting () kde ! org>
Date:       2020-10-22 17:15:19
Message-ID: CADWV2K6Zgv=9TwfJEOXvoKFbO645t=kFrGxi8Cug34qwnd9GtQ () mail ! gmail ! com
[Download RAW message or body]

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@kde.org> wrote:

> On Fri, Oct 23, 2020 at 6:08 AM Michael Reeves <reeves.87@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
>

[Attachment #3 (text/html)]

<div dir="ltr"><div class="gmail_default" style="font-family:monospace">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&#39;s notarization service \
so they can check it doesn&#39;t use any apis that it shouldn&#39;t or something, \
then the .app needs to be &quot;stapled&quot; with the notarization before putting it \
into the dmg. That said iirc signing the app is a requirement before submitting the \
app to apple&#39;s notarization service in the first place.</div></div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Oct 22, 2020 at 11:12 \
AM Ben Cooksley &lt;<a href="mailto:bcooksley@kde.org">bcooksley@kde.org</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div \
dir="ltr">On Fri, Oct 23, 2020 at 6:08 AM Michael Reeves &lt;<a \
href="mailto:reeves.87@gmail.com" target="_blank">reeves.87@gmail.com</a>&gt; \
wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div dir="auto">Could someone familiar with the CI \
and OS X signing machinism look at this.<div dir="auto"><br></div><div dir="auto"><a \
href="https://bugs.kde.org/show_bug.cgi?id=428062" \
target="_blank">https://bugs.kde.org/show_bug.cgi?id=428062</a><br></div><div \
dir="auto"><br><div dir="auto">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.</div></div></div></blockquote><div><br></div><div>This is because Craft to \
my knowledge at this time does not support notarization of MacOS \
binaries.</div><div><br></div><div>Once that has been added, the issue should \
disappear.</div><div><br></div><div>Regards,</div><div>Ben  </div></div></div> \
</blockquote></div>



[prev in list] [next in list] [prev in thread] [next in thread]