![]() Doing so requires some significant changes to what/how we customize our application, but we are working hard to maintain all functionality at this point. However, the release of Mojave changes that calculation for the following reason: permissions granted to unsigned applications to not persist upon reinstall.This is the main reason why we have decided to investigate signing the installer. ![]() pkg to have customized branding, naming, etc. Therefore, not signing the application was a tradeoff to allow for the. However, only for macOS do these changes break the signature of the bundle. The same is true for all of the installers. When the macOS installer bundle is downloaded, it undergoes dynamic changes related to our customization features. We have started development on signing the macOS installer bundle. I enjoy all the feedback we have gotten on this issue. As we continue development on this issue, I wanted to provide some clarification. Thank you for considering my feedback on this. app that needs to be signed, not the installer. If that is at all helpful, please don't hesitate to contact me. I'd love to work with you and your team more directly to make sure this comes to light. While I agree signing the application in and of itself not enough, if you have an Apple MDM setup and deploy your own privacy policy that whitelists the application (a signed application is required), then you can remotely approve the use of CW Control *without* any user intervention on the first connection. Let me try to help by providing some reading material: Your team unfortunately did not research extensively enough. I respectfully reject your assertions that this isn't possible. I know this is in fact possible, as I've seen it working (with other applications and with your application when signed). I'd like to encourage your team to not give up. I tried posting this as a reply above, but it has been stuck in moderation for 2 days now. The team has also planned performance enhancements and improvements to the Mac client, and will communicate more Mojave updates as they become available. After extensive research, the team has determined that this requirement is mandatory on the first connection signing the application or access agent will not solve this issue.ĬonnectWise Control is actively researching the best way to manage the Gatekeeper feature and improve the experience when updating or reinstalling an access agent on macOS Mojave. The steps to control a macOS Mojave session have been outlined in documentation. When first connecting to a macOS Mojave session, end users must physically allow access to the ConnectWise Control app from the machine itself. ![]() One of these new challenges is a change in the way hosts gain control of Mojave devices. These new security and privacy settings were enacted by Apple and change how all vendors of remote control products are able to deploy to endpoints. The team at ConnectWise Control is working to ensure that these changes have the least amount of impact possible for partners. Apple’s recent release of the Mojave operating system introduces new features and security measures, offering end users more peace of mind but also introducing new challenges to partners supporting Apple machines.
0 Comments
Leave a Reply. |