Dropbear ssh tunneling segfault
Matt Johnston
matt at ucc.asn.au
Wed Mar 21 22:08:41 AWST 2018
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 much experience with that though, sorry.
https://source.android.com/security/selinux/device-policy
Cheers,
Matt
On 21 March 2018 9:20:38 pm AWST, Hayk Beglaryan <hayk.beglaryan7 at gmail.com> wrote:
>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_key root at localhost -p 56048 df” doesn’t
>work at all.
>
>Regard,
>Hayk
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ucc.gu.uwa.edu.au/pipermail/dropbear/attachments/20180321/ebb49438/attachment-0001.htm
More information about the Dropbear
mailing list