check quarantine issues on newer MacOS

[ramagottfried]

I had my students install the latest release today and some where having issues with the OS quarantining objects -- I'm still on 10.14 so haven't seen this, but maybe good to test on the latest OSs to make sure the externals are signed, or whatever is required now.

apparently there is a window that pops up whenever they make a new odot object

[maccallum]

@wagne342, is there any news on this front?

The problem is the worst on Catalina. On Big Sur, it's not terrible--you get a popup the first time you try to load an object that's in quarantine, and there's an option to have Max remove the quarantine flag from all the objects used in your patch, so at least you don't have to click through for every one. But it'd certainly nice to actually have everything code signed...

[maccallum]

@equilet and @wagne342, I'm wondering about the timeline for this. Is it feasible to consider having this done before the release into the package manager? Or the other way around--is this it a deal-breaker to release non-code signed objects in the package manager?

[dmuhr]

Hello everyone, Just wanted to comment that using odot objects in Catalina is becoming incredibly difficult. Every time I open a patch with odot objects, I need to run sudo xattr -rd com.apple.quarantine in the terminal for each object. Is there an easier way?

Thanks !

[equilet]

Hi all - apologies for the late reply on this.
I've confirmed with C74 that when releasing via the PM, that quarantining/codesigning is handled by them. This is not an issue w/ the current release outside of sending people test builds.

Separately, it's my understanding that @wagne342 is working on getting the developer status fixed with Apple.

[wagne342]

I am still trying to get an answer from the Sponsored Projects Office on how to proceed. The Apple developer ID needs to be associated with a Dun and Bradstreet D.U.N.S. number. Campus has a DUNS number but I'm not certain we are allowed to use it or if we need to/are allowed to get our own. I have reached out again yesterday to SPO for guidance on this, but haven't heard back yet. Concurrently, I have reached out to Apple for clarification on whether CNMAT needs to apply for its own DUNS number. This appears to be the only hangup at the moment. Aside from this one issue we are totally able to meet all other criteria for gaining Apple Developer status AFAIK. This should be resolved shortly

…

On Thu, Apr 15, 2021 at 10:35 AM Jeffrey Lubow ***@***.***> wrote: Hi all - apologies for the late reply on this. I've confirmed with C74 that when releasing via the PM, that quarantining/codesigning is handled by them. This is not an issue w/ the current release outside of sending people test builds. Separately, it's my understanding that @wagne342 <https://github.com/wagne342> is working on getting the developer status fixed with Apple. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#418 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGWSI57LJH3EY4IBE7NXC3TI4PURANCNFSM42TSMOWA> .

-- Jeremy Wagner, PhD Composer/Musician/etc. ***@***.*** www.jeremywagner.info soundcloud.com/jeremy-l-wagner/

[wagne342]

Update: I spoke with Dun & Bradstreet this afternoon and they have agreed to issue CNMAT its own D.U.N.S. number which should be in place in the next two business days. We will work to provide proper validation and next steps as required by the various UC policies. I have also reached out again to IPIRA to make sure the project is properly recorded and that all software authors are properly credited.