Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

hasAdbInEmulator misfires (or logic is wrong?) for tcpip adb connections #11

Open
strazzere opened this issue Sep 18, 2019 · 1 comment
Assignees
Labels

Comments

@strazzere
Copy link
Owner

V/AntiEmulator(15537): Checking for QEmu env...
V/AntiEmulator(15537): hasKnownDeviceId : false
V/AntiEmulator(15537): hasKnownPhoneNumber : false
V/AntiEmulator(15537): isOperatorNameAndroid : false
V/AntiEmulator(15537): hasKnownImsi : false
V/AntiEmulator(15537): hasEmulatorBuild : false
V/AntiEmulator(15537): hasPipes : false
V/AntiEmulator(15537): hasQEmuDriver : false
V/AntiEmulator(15537): hasQEmuFiles : false
V/AntiEmulator(15537): hasGenyFiles : false
V/AntiEmulator(15537): hasEmulatorAdb :true
V/AntiEmulator(15537): hitsQemuBreakpoint : false
V/AntiEmulator(15537): QEmu environment detected.
shell@hammerhead:/ $ cat /proc/net/tcp
  sl  local_address rem_address   st tx_queue rx_queue tr tm->when retrnsmt   uid  timeout inode                                                     
   0: 00000000:15B3 00000000:0000 0A 00000000:00000000 00:00000000 00000000  2000        0 106221 1 00000000 100 0 0 10 -1                           
   1: 2901A8C0:A572 33DB1CB8:01BB 01 00000000:00000000 00:00000000 00000000 10095        0 106752 1 00000000 22 4 32 10 -1                           
   2: 2901A8C0:15B3 5E01A8C0:889E 01 00000018:00000000 01:00000014 00000000  2000        0 109277 3 00000000 21 4 29 10 -1                           
   3: 2901A8C0:DAE7 2D00D9AC:01BB 08 00000000:0000026D 00:00000000 00000000 10022        0 24576 1 00000000 21 4 30 10 -1                            
   4: 2901A8C0:C6F4 D088592F:01BB 09 00000001:00000000 01:000007E2 00000007     0        0 0 2 00000000 3584 4 14 2 7                                
   5: 2901A8C0:9A34 3BDB1CB8:01BB 01 00000000:00000000 00:00000000 00000000 10095        0 109637 1 00000000 21 4 33 10 -1             
@strazzere strazzere added the bug label Sep 18, 2019
@strazzere strazzere self-assigned this Sep 18, 2019
@strazzere
Copy link
Owner Author

I guess I'm not realizing that this is a somewhat flawed assumption. It relies on "real" devices not having the concept of tcp adb connections - which isn't true. However, it's usually pretty true that a device running around in the field would not have adb bound to a tcp port unless someone is using it to debug things... Need to think on this one a bit more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant