Cannot install Helper (Mac App Store)
-
could you try re-downloading, and re-installing the helper (i uploaded a new version):
https://sweetpproductions.com/products/wifispoof3/CookieScripts.dmgit will have a pink icon
-
sorry bad link, try this one:
https://sweetpproductions.com/products/wifispoof3/WiFiSpoofMASHelper.dmg -
Still no luck. So I initially installed the Helper and it didnt work. So deinstalled both and restarted the computer.
Installed WifiSpoof v3.0 and the Helper. The buttons are still greyed out and the WifiSpoof app is still inviting me to install the helper?
-
if you wanted to email me, it would be perhaps faster
support@sweetpproductions.com -
this should be fixed now
I have uploaded v3.0.1 to my server with a fix for the code signing issues.
https://sweetpproductions.com/products/wifispoof3/WiFiSpoof3.dmgI have also updated the MAS Helper App to version 1.0.1 for Mac App Store users.
https://sweetpproductions.com/products/wifispoof3/WiFiSpoofMASHelper.dmg
-
sorry bad link, try this one:
https://sweetpproductions.com/products/wifispoof3/WiFiSpoofMASHelper.dmg -
That is not quite the intent of an XPC process. You can definitely use an XPC process if you want, but an XPC alone isn't going to help you escape the sandbox. It is possible and explicitly allowed for Mac App Store apps to have plug-ins that can escape the sandbox. But I am unaware of any Apple framework that is explicitly designed to help you do that. Also, for the Mac App Store, you will have to design your app carefully so that it has an acceptable level of functionality without the plug in.
But if you can handle all that, then you can design your plug-in however you want. There are numerous ways to have the plug-in and your sandbox app work together. Personally, I wouldn't recommend scripting because that is hard to do and fairly limited. Once you leave Apple's approved and intended path, Apple doesn't help you anymore, but then you're free to do whatever you want. Some suggestions would be a command line tool that accepts arguments, or a command line tool that can communicate over an open pipe with the sandboxed app. There will, of course, be limitations on sandboxed side.
-
That is not quite the intent of an XPC process. You can definitely use an XPC process if you want, but an XPC alone isn't going to help you escape the sandbox. It is possible and explicitly allowed for Mac App Store apps to have plug-ins that can escape the sandbox. But I am unaware of any Apple framework that is explicitly designed to help you do that. Also, for the Mac App Store, you will have to design your app carefully so that it has an acceptable level of functionality without the plug in.
But if you can handle all that, then you can design your plug-in however you want. There are numerous ways to have the plug-in and your sandbox app work together. Personally, I wouldn't recommend scripting because that is hard to do and fairly limited. Once you leave Apple's approved and intended path, Apple doesn't help you anymore, but then you're free to do whatever you want. Some suggestions would be a command line tool that accepts arguments, or a command line tool that can communicate over an open pipe with the sandboxed app. There will, of course, be limitations on sandboxed side.
@kimedzheeran I don't remember exactly why I utilised an XPC service (its been a while since I looked at the codebase), But I think it was more for privilege escalation. Without it, you would need to enter your password every time to change the Mac address - which is not exactly user friendly.
