[MacPorts] #70232: Many, maybe all, binaries generating "code object is not signed at all" -67062 errors in Console

[MacPorts]

#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:  buildbot/mpbb                        |    Version:  2.9.3
 Keywords:  67062 signing signed certificate     |       Port:
  error taskgated console                        |
-------------------------------------------------+-------------------------
 Hello :)

 First of all, I'm unsure where this report belongs. I was on github, and
 thought the issue ought to be reported on the "mpbb" repo, but tickets
 apparently need to be made here. Also, I don't know if this is just on
 High Sierra, or perhaps on all targets, but either way, this is the thing:

 I was trying to debug a wholly unrelated issue, and was befuddled about a
 seemingly endless stream of "taskgated: MacOS error: -67062" errors.

 Google led me to a perl script here:
 https://apple.stackexchange.com/a/411062/35944 . This allows me to get
 details on which binaries are causing these errors as they occur. The
 results is that I found that it **seems like** (not necessarily is so)
 that none of the binaries I've installed from MacPorts have been signed at
 all. coreutils, findutils, git, par2, cksfv, zsh, etc. All generate a
 -67062 error as they're executed.

 I know that this isn't a functional problem, as the binaries will run just
 fine. But the extreme amount of errors generated because of this clutters
 the log, and makes it really difficult to use the log to debug other
 issues. I'm thinking it must have some impact on performance as well.

 In the StackExchange answer I linked to, the poster also points to the
 solution: Simply sign the binary with any certificate, even a self-signed
 one.

 I guess could do this myself, but for one, I'd need to then re-sign port
 binaries after every install and update, and also it seems like it's a bug
 or bug-like issue with MacPorts, at least on High Sierra binaries, that
 you might want to know about, so here's the report :)

 Thank you for a fantastic software manager, and for your dedication to
 supporting legacy OSes!

 Silas

-- 
Ticket URL: <https://trac.macports.org/ticket/70232>
MacPorts <https://www.macports.org/>
Ports system for macOS