Post not yet marked as solved
I don't know if this is the same situation I had early on, but when I was in the compile/link/install/run/uninstall/repeat loop, if I didn't reboot after the uninstall, that removal would queue up. After half a dozen or so loops, I'd have a list of extensions ready to uninstall on reboot. I'd reboot and one would be gone, reboot again and another would be gone. I'd have to keep rebooting to get rid of them one by one.
Like I said, this was a while ago and I've gotten into a habit of either restarting the VM or restoring the snapshot. Not sure if this is what you're seeing or not.
Post not yet marked as solved
Well, the Forums are now broken. Search only works if you know what you're looking for. Browse is the way to find new things you didn't know about.
I think that is a ES_EVENT_TYPE_AUTH_RENAME event. I don't have anything setup right now to verify this, but if you think about how you'd do it from a command line, you'd use a mv command to either rename the file or move it to another location, i.e., the trashE.g., my code has this in the rename event handler if (msg->event.rename.destination_type == ES_DESTINATION_TYPE_NEW_PATH)We're checking to see if there's a new path. Just look to see if someone is moving the file you care about somewhere else.
Post not yet marked as solved
Thanks, Quinn. I actually got a response back from our Apple rep who said that since we're not MAS, we can make the NE unsandboxed and it should work.I'll let you know how it goes when I get there, fighting another fire at the moment.
Post not yet marked as solved
Hi Quinn,Does this imply that you cannot have both an ES and NE solution in one binary that can be delivered to our customers? Our controlling app assumes one connection to the driver and will be unpleasant to rewrite the comm part for macOS only.Thanks
I don't know if that's the only answer, but it's what I've found by reading the forums and experimentation. If you, or anyone, finds some definitive documention, please post a link here. I'd love to read it and let our support team know when we release our product into the wild.
Post not yet marked as solved
What I've found is that you need to keep rebooting, they disappear one at a time and not all at once. If I forget to do a snapshot of my VM before a day of testing, I've found myself just sitting there at lunch restarting, time after time, until they're gone, just to make sure I have clean slate.
Post not yet marked as solved
I'm glad I could help with the MachServiceName, good luck with the rest. Took me many days and attempts (wiping out all certs/app ids/profiles and creating them again and again) to get something that would build and run successfully. I got it running with SIP disabled first and was able to get everything stable, it took 2 months to get approval from Apple to give my personal account the endpoint security entitlement to run with SIP enabled. The only problem I had there was that my test VM wasn't in my device list, therefore not in the provisioning profile. When I tried to run it there, it wouldn't work. Not sure of the exact error. That was a couple of weeks ago. Just look at any and all logs, all the different forums here (especially posts by eskimo), and try to read between the lines.Again, good luck!
Post not yet marked as solved
I have these 3 settings (edited to protect the innocent) <key>NSEndpointSecurityMachServiceName</key> <string>My Bundle ID here</string> <key>NSEndpointSecurityRebootRequired</key> <false/> <key>NSEndpointSecurityEarlyBoot</key> <true/>Not sure if you need or want them all.
Thank you, Quinn. This is going onto my notes page right now 🙂
I have a question since I know almost nothing about Swift. When you create the array8 buffer by passing socketFlow.sourceAppAuditToken! into Array, is it passing the data bytes from the socketFlow.sourceAppAuditToken NSData object or the NSData object itself? I'm not sure how all this "unwraps" in Swift or exactly how you'd tell it to use the data bytes.I'm learning Swift as I go and was just wondering how it processes things like that.Thanks
Hi Quinn,Yes, Xcode 11.4 beta 3 (11N132i), running on 10.15.4 Beta (19E258a)So, it's not a clock time, but a run time? I.e., it starts ticking on boot and pauses when it's asleep. I use the deadline and mach_time values to calculate a timeout value that I use to make sure we answer in time. Already had a timeout check, just updated it to use the MIN of this value (minus 1 second for a cushion) and our normal timeout value. But still occasionally see the above error message in the log after wakeup or resuming the VM after suspending it. Just made me wonder and post this question.Thanks
When you retire Quinn, 3rd party macOS development will grind to a halt 😉 No one will be able to figure out anything without your help.
