Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 2 replies
  • Subscribers 6 subscribers
  • Views 7638 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SMC 5.1.3 (rev 3921) - Root rights detected

BenesJ

Hi all,

 I have one question on you If someone find this problem or solution. 

 After update to new 5.1.3 we found that on mobil phone Jiayu S3 LTE (And 4.4.4) and Lenovo Yoga Tablet 2 (And 4.4.2)  compiance violation Root rights detected but there is no app which need root rights (checked).

Other devices are OK (same or different Android versions)

Only these 2 have some kind of problem.

Ty for your answer

Jakub

:58094


This thread was automatically locked due to age.
Parents
  • 0

    Hi Jakub,

    the SMC server version has in general nothing to do with the root right detection.

    The root right detection is performed directly on the device by the SMC client directly.

    With SMC 5 we have added some additional checks for root rights which are executed by the SMC client.

    If one of these checks apply for the device, it is shown as rooted.

    You can get an SMC Android client log and directly check what is causing the violation. How to get a log of the SMC Android client is explained in this article. Within this log, you might find lines like these:


    INFO [SMC Device]: found rooting indicator: no exception was thrown by executing 'busybox' command
    INFO [SMC Device]: found rooting indicator: no exception was thrown by executing 'su' command
    INFO [SMC Device]: found rooting indicator: file '/system/xbin/su'

    Hope this helps.

    Best regards

    Stefan

    :58101
Reply
  • 0

    Hi Jakub,

    the SMC server version has in general nothing to do with the root right detection.

    The root right detection is performed directly on the device by the SMC client directly.

    With SMC 5 we have added some additional checks for root rights which are executed by the SMC client.

    If one of these checks apply for the device, it is shown as rooted.

    You can get an SMC Android client log and directly check what is causing the violation. How to get a log of the SMC Android client is explained in this article. Within this log, you might find lines like these:


    INFO [SMC Device]: found rooting indicator: no exception was thrown by executing 'busybox' command
    INFO [SMC Device]: found rooting indicator: no exception was thrown by executing 'su' command
    INFO [SMC Device]: found rooting indicator: file '/system/xbin/su'

    Hope this helps.

    Best regards

    Stefan

    :58101
Children
No Data
Unfiltered HTML