I’d suggest that someone else (I’ll volunteer) run the 4.1.2 build.

This sounds like a great idea! Are there private keys or something that would prevent this?

Yes and no. The current osquery mac packaging is signed with Teddy’s personal key. Obviously I can’t sign it with that, but I can sign it with mine. But even knowing that we can get that far is progress.

Signing with another key will mean that admins may need to Deploy a new TCC profile for FDA , worth mentioning in the release notes this is for Mojave / Catalina

My gut sense is that it’d be better to wait, but have the option.

Worth chipping in some cash for an OSquery specific dev account and eating the pain once for the move to an organisation shared Cert ?

I have been slowly working through https://github.com/osquery/foundation/issues/3

Hmm DUNs is a pita

Nah. It’s fine. Just lots of bits I had to work through