I am on High Sierra, and I have opened Console. I am seeing TONS of authd : MacOS error -67050 and sometimes -67062. Sometimes I see this on taskgated and also iCal.
What can I do to trace what causes this?
Ask Different is a question and answer site for power users of Apple hardware and software. It only takes a minute to sign up.
Sign up to join this communityI am on High Sierra, and I have opened Console. I am seeing TONS of authd : MacOS error -67050 and sometimes -67062. Sometimes I see this on taskgated and also iCal.
What can I do to trace what causes this?
This error occurs when unsigned code is run. The taskgated process is the one checking if the executable is signed. In order to check, it must open the file. So to track down what is being opened by the process you can use dtruss (you may have install the Xcode command line tools to get it). Just create the following file named unsigned.pl:
#!/usr/bin/perl
use strict;
use warnings;
open my $fh, "-|", "dtruss -p `ps -ef | grep taskgated | grep -v grep | awk '{print \$2}'` -t open 2>&1";
while (my $line = <$fh>) {
my ($file) = $line =~ /open\("(.*)\\0"/;
next unless defined $file and -f $file;
my $signed = qx/codesign -dvvv "$file"/;
print $signed;
}
Which can be run like this:
sudo perl unsigned.pl
and it will spit out lines like
/path/to/executable: code object is not signed at all
You can then create a self signed cert with Keychain Access:
Once you have a self-signed cert you can sign the executables in the terminal with
codesign -s codesigner /path/to/executable
Note: you will see a lot of examples using -f, but that forces it to be resigned with the new cert. If you have lost access to the cert, or if the cert has expired, that might be necessary, but I try to avoid it.
ps ...
commands between the back ticks can be replaced with pgrep taskgate
. • Those commands get the Proccess ID of taskgated. • pgrep
gets the PID of any process whose name contains the search expression.
Jan 25, 2021 at 3:04