sectroyer wrote:I think with this changes sftp worked for me on E... Let's test it more carefully run this:
Code: Select all
/bin/ps | grep dropbear
killall -KILL dropbear
/bin/ps | grep dropbear
dropbear -F -E
and then try to use sftp in other terminal window. BTW why do you want to use sftp if you have ftp and scp ?

It's sftp very good if you want to connect securely from outside if you using windows workstation + filezilla for example.
I am sure that nobody will keep the tv powered all of the time, but for emergency purposes, why not.
It's not mandatory but is good to have it.
Code: Select all
root@tv:/mnt # /bin/ps | grep dropbear
1814 root 0:00 dropbear
3419 root 0:00 grep dropbear
root@tv:/mnt # killall -KILL dropbear
root@tv:/mnt # /bin/ps | grep dropbear
3439 root 0:00 grep dropbear
Code: Select all
Status: Connecting to 192.168.0.101...
Response: fzSftp started
Command: open "root@192.168.0.101" 22
Command: Pass: ******
Status: Connected to 192.168.0.101
Error: Connection closed by server with exitcode 127
Error: Could not connect to server
Code: Select all
root@tv:/mnt # dropbear -F -E
[3466] Jun 22 17:03:12 Failed reading '/etc/dropbear/dropbear_dss_host_key', disabling DSS
[3466] Jun 22 17:03:12 Not backgrounding
[3504] Jun 22 17:04:28 Child connection from 192.168.0.17:54898
[3504] Jun 22 17:04:28 Password auth succeeded for 'root' from 192.168.0.17:54898
[3504] Jun 22 17:04:28 Exit (root): Exited normally
[3512] Jun 22 17:04:33 Child connection from 192.168.0.17:54899
[3512] Jun 22 17:04:34 Password auth succeeded for 'root' from 192.168.0.17:54899
[3512] Jun 22 17:04:34 Exit (root): Exited normally