1 3 4 5 6 7 Previous Next 78 Replies Latest reply on Jun 30, 2020 10:42 AM by chengtmskcc Go to original post
      • 75. Re: iOS 13 Devices Marked as Compromised
        alldaymcrae Novice
        Our use case is a little different at the time of the IOS release. We just started running into this about 3 weeks ago. I only have about 1//2 a department using boxer at this time we were still in the testing phases when 13x first came out so it was just me and few people that even had boxer. The rest are still using the Native Mail App across the company. But I agree, it is concerning and frustrating that its been an issue for over two months and they still don't have resolution yet. . At this time I have the time to wait because of the holidays but yea if this is still a thing 2 more months from now we will end up going a different direction.

        • 76. Re: iOS 13 Devices Marked as Compromised
          ThomasBeckerThomasBecker1 Novice
          I got my issue fixed by VMware last Friday. We had to set a bypass rule in the network traffic settings for VMware Tunnel for the following urls.
          api.na1.region.data.vmwservices.com
          discovery.awmdm.com
          signing.awmdm.com
          With that in place Boxer no longer reported a compromise. It looks like that Boxer has to do some online checks for the compromised detection. I don't know why this can't be done offline but it work for us so far. Support told me that this workaround will be implemented in the next Boxer release so you don't have to set a bypass rule.
          • 77. Re: iOS 13 Devices Marked as Compromised
            alldaymcrae Novice
            Thomas  B - Are you hosted or on-prem?
            • 78. Re: iOS 13 Devices Marked as Compromised
              AdamBarlow Lurker
              Thomas' solution also worked for us. I created a bypass rule for client traffic for Boxer with the listed URLs. We are running in the hosted environment. Thanks for the update Thomas.
              • 80. Re: iOS 13 Devices Marked as Compromised
                GuenterGruber Novice

                Thomas B. I´m not sure if the workaround will help in my configuration. We do not use the boxer, so it´s rather the hub-app that triggers the compromised status.
                What I also found out was that the status switched on some devices more than one time from true to false and back to true - but could not find any reason for that change. Some times it helps to start the hub and force a sync, somtimes a restart of the device helps, and on other devices nothing will help...
                So at this time I will wait for a new hub-(or iOS) version, the compromised-status is a ' beauty mistake'  without impact.

                • 81. Re: iOS 13 Devices Marked as Compromised
                  MarkSchwantje Enthusiast
                  Thomas B/Adam B - Do you have Boxer configured with per-app VPN? Trying to understand the correlation between Boxer and VMware Tunnel.

                  Guenter G - According to AirWatch support, Hub is the only app that supposedly contains the ' fix'  to the SDK incompatibility issue. Assuming what they have told me is correct, waiting for a new version of Hub isn't going to help you.
                  • 82. Re: iOS 13 Devices Marked as Compromised
                    ThomasBeckerThomasBecker1 Novice
                    Mark S.
                    Yes, we use Boxer as per-app VPN with Tunnel. The mail settings are in the Boxer app configuration. We also do not use the SEG.
                    • 83. Re: iOS 13 Devices Marked as Compromised
                      GuenterGruber Novice

                      Mark S - in this case my fist question is: ' what have they fixed?' . Every day the number of compromised devices on my dashboard increases. The good message is, this is currently the only negativ impact.
                      The next question is: why are not all of my ~16.000 devices affected? They all using also the last HUB-Version...


                      With the beta version of iOS 13.0, nothing like this has been noticed yet, only since the first official version was available the compromised devices appeared (whit the ' on-off'  effects I wrote in my last message)...

                      • 84. Re: iOS 13 Devices Marked as Compromised
                        MarkSchwantje Enthusiast
                        Guenter G - I'm just relaying the message. Honestly, given their lack of transparency regarding the matter, I don't think they even know what is causing it let alone have a fix for it.

                        Mark
                        • 85. Re: iOS 13 Devices Marked as Compromised
                          MarkSchwantje Enthusiast
                          We are still being plagued by this issue, despite all the AirWatch apps supposedly now containing the fix for this issue. With a recent campaign to get all of our users updated to iOS 13.3, we've seen a considerable increase in the number of devices being detected as compromised. Now the fix seems to be to uninstall/reinstall the Hub app, despite it already being on the latest version.

                          Anyone else seeing this?
                          • 86. Re: iOS 13 Devices Marked as Compromised
                            Stansfield Hot Shot
                            We gave up and stopped having it do anything a while back sometimes just re-opening the apps will clear compromised but not always
                            • 87. Re: iOS 13 Devices Marked as Compromised
                              alldaymcrae Novice
                              Not the exact problem and it depends on your setup but if you're using the VMware tunnel and Boxer they require the Hub app to be on the device and and on latest version. There is a direct correlation with Boxer and Hub app though if you have that setup. In regards to Compromised devices that has only happened to one user over the last month but that user didn't have the hub app installed. Since making sure that its installed everywhere and then also we turned off everything in regards to compliance we haven't seen the issue for about 2 weeks now   We don't use VMware Tunnel so according to the support tech  we don't need to worry about the Hub app but I'm currently work with there support to get it working correctly after enrollment because there is another bug with it not allowing a user to login after enrollment. It works fine to enroll but after enrollment it doesn't authenticate using the default SDK profile setup. Content locker uses that currently and it works fine.
                              • 88. Re: iOS 13 Devices Marked as Compromised
                                MarkSchwantje Enthusiast
                                Jeremy - We use VMware Tunnel and Boxer, but we don't have Boxer configured to use Tunnel (its not enabled for per-app VPN). All AirWatch apps are up to date when these false-positive detections take place.
                                • 89. Re: iOS 13 Devices Marked as Compromised
                                  Stansfield Hot Shot
                                  Has anyone had trouble with lost mode randomly enabled by the system (shows as by sysadmin in logs) support says we are the only ones it seems to be linked with an app issue even though all apps are updated and compromised detection and app passcodes are turned off it acts like the passcode trips while being off?  It usually marks the device as compromised so I thought it might be linked with this.  We do not have ssl pinning enabled (not sure if that has anything to do with anything but it might affect apps behavior)
                                  1 3 4 5 6 7 Previous Next