<html><head></head><body>I suspect selinux is blocking something, after dropbear forks to run the shell. Can you find where selinux keeps its logs?<br>
When you run 'su' it enters a less restrictive context than normal root, so it runs ok.<br>
<br>
I guess you need to create a selinux policy for the dropbear service - i don't have much experience with that though, sorry.<br>
<br>
<a href="https://source.android.com/security/selinux/device-policy">https://source.android.com/security/selinux/device-policy</a><br>
<br>
Cheers,<br>
Matt<br><br><div class="gmail_quote">On 21 March 2018 9:20:38 pm AWST, Hayk Beglaryan <hayk.beglaryan7@gmail.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">Dear Matt,<br><br>Thanks for fast reply. <br>[1] Yes I run dropbear from adb shell and it’s works correctly. My steps are followings: <br> $ adb connect [device ip]<br> $ adb shell<br> # su<br> # dropbear -E -R<br><br>[2] Please find requested logfile1.txt attached.<br><br>[3] Running "ssh -i ssh_rsa_key root@localhost -p 56048 df” doesn’t work at all.<br><br>Regard,<br>Hayk <br><br></pre></blockquote></div></body></html>