I suspect selinux is blocking something, after dropbear forks to run the shell.
Can you find where selinux keeps its logs?
When you run 'su' it enters a less restrictive context than normal root, so it
runs ok.
I guess you need to create a selinux policy for the dropbear service - i don't
have
Dear Matt,
Thanks for fast reply.
[1] Yes I run dropbear from adb shell and it’s works correctly. My steps are
followings:
$ adb connect [device ip]
$ adb shell
# su
# dropbear -E -R
[2] Please find requested logfile1.txt attached.
[3] Running "ssh -i ssh_rsa_k
Hi Hayk,
I wonder if a service running from init.rc has different restrictions on what a
process is allowed to do. Maybe a syscall that usually succeeds is blocked by
the system, and Dropbear doesn't handle it well. When you run it manually you
are running it under adb?
Can you make your myScr
