ssh: connect to host 10.176.79.176 port 22: Connection refused

[tr4v3ler]

Due to environmental limitations, I can only connect to Android devices through TCP. I wrote a script to automatically execute adb connect 10.176.79.176:8888 commands to ensure that syzkaller can access the device through adb. However, there was an SSH error here. I don't understand why using adb involves SSH. How can I solve this problem? The attachment is the log and configuration file for executing syzkaller. By the way, 10.176.79.176 is the IP address of my Windows PC, and my Android device is plugged into this Windows PC, while syzkaller runs on another Linux PC. I use a series of port forwarding to allow the Linux PC to access the Android device through a certain port on the Windows PC.

[Aleksandr Nogikh]

On Sat, Aug 19, 2023 at 7:28 AM tr4v3ler <0xtr4...@gmail.com> wrote:
>
> Due to environmental limitations, I can only connect to Android devices through TCP. I wrote a script to automatically execute adb connect 10.176.79.176:8888 commands to ensure that syzkaller can access the device through adb. However, there was an SSH error here.

> I don't understand why using adb involves SSH.

syz-manager (on host) communicates with syz-fuzzer (on devices) via
SSH. In this case, via `adb shell`.

> How can I solve this problem? The attachment is the log and configuration file for executing syzkaller. By the way, 10.176.79.176 is the IP address of my Windows PC, and my Android device is plugged into this Windows PC, while syzkaller runs on another Linux PC. I use a series of port forwarding to allow the Linux PC to access the Android device through a certain port on the Windows PC.

I think the IP should be the IP address of your device, not of your host.

[tr4v3ler]

Yes, I am currently limited by the environment and can only plug Android devices into a Windows PC. If I want to perform Fuzzing test on Android devices through a Linux PC, I can only indirectly connect to Android devices through a Windows PC port.

[tr4v3ler]

I have used this method in the past, but there have been no SSH errors before.