swda CLI executable won't run because it isn't signed.

[seancolins]

Not sure why, but the SWDA executable will not run because of a signature problem. Is anyone else aware of this, and found a work around for mass deployment?

[kbluck]

You can fix this locally with:
xattr -d com.apple.quarantine /path/to/swda

The app does seem to be correctly signed and notarized as far as I can tell. I tried screwing around with spctl and adding a rule didn't work, even disabling GateKeeper completely didn't work. So, something about the file having this extended attribute added due to being downloaded. I don't know if that's something that can even be fixed in the build.

[seancolins]

That’s a bummer. OK, thanks. On May 20, 2022, at 12:22 PM, Kevin Bluck ***@***.******@***.***>> wrote: You can fix this locally with: xattr -d com.apple.quarantine /path/to/swda The app does seem to be correctly signed and notarized as far as I can tell. I tried screwing around with spctl and adding a rule didn't work, even disabling GateKeeper completely didn't work. So, something about the file having this extended attribute added due to being downloaded. I don't know if that's something that can even be fixed in the build. — Reply to this email directly, view it on GitHub<#58 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMQJ25CNNPNAJGP7PCBSS6DVK7RAXANCNFSM5VDOFYSA>. You are receiving this because you authored the thread.Message ID: ***@***.***>