[MacPorts] #70232: Many, maybe all, binaries generating "code object is not signed at all" -67062 errors in Console
MacPorts
noreply at macports.org
Mon Jun 17 11:27:46 UTC 2024
#70232: Many, maybe all, binaries generating "code object is not signed at all"
-67062 errors in Console
---------------------+---------------------
Reporter: 1dolla | Owner: admin@…
Type: defect | Status: new
Priority: Low | Milestone:
Component: base | Version: 2.9.3
Resolution: | Keywords:
Port: |
---------------------+---------------------
Comment (by 1dolla):
Replying to [comment:1 ryandesign]:
> To which log are you referring?
>
> On Apple Silicon, all binaries are signed because they cannot run
otherwise. This is accomplished automatically by the compiler, linker,
etc. and no extra code was added to MacPorts to accomplish this. On Intel
and PowerPC processors, nothing MacPorts installs is signed, unless a
port's build system specifically does so, and we were not aware of any
negative consequences of that.
Sorry, this is on Intel. I navigated to the High Sierra section in the
issues tree before searching and eventually clicking "New ticket," so I
thought I was creating a High Sierra-specific ticket, but of course it
doesn't work like that :)
I was referring to the system log that display in Console. Not sure what
this is in other terms, I'm mostly used to Linux logs.
Replying to [comment:2 ryandesign]:
> mpbb just runs MacPorts to install ports. If everything needs to be
signed, it would happen in MacPorts base.
Thank you for moving my ticket.
I tried signing all the MacPorts binaries with a self-signed code
signature certificate, and this has gotten rid of the taskgated error
messages in Console, but of course this is just a temporary fix on my end.
Thanks again :)
--
Ticket URL: <https://trac.macports.org/ticket/70232#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list