View Single Post
Old 05-04-2023, 09:42 PM   #1
elinkser
Addict
elinkser has survived committing the World's Second Greatest Blunder.elinkser has survived committing the World's Second Greatest Blunder.elinkser has survived committing the World's Second Greatest Blunder.elinkser has survived committing the World's Second Greatest Blunder.elinkser has survived committing the World's Second Greatest Blunder.elinkser has survived committing the World's Second Greatest Blunder.elinkser has survived committing the World's Second Greatest Blunder.elinkser has survived committing the World's Second Greatest Blunder.elinkser has survived committing the World's Second Greatest Blunder.elinkser has survived committing the World's Second Greatest Blunder.elinkser has survived committing the World's Second Greatest Blunder.
 
Posts: 242
Karma: 146236
Join Date: Oct 2022
Device: Kobo Clara HD
Invoking KOReader's Dropbear SSH server from NickelMenu

Here's something weird:


If I run the Dropbear SSH server from inside KOReader, then exit KOReader, I can connect with an SSH client by password authorization (whether the client is laptop or phone).

But if I run the exact same command to invoke Dropbear as KOReader uses, except from NickelMenu, then I can't connect.

This is my NickelMenu entry for Dropbear, copied from the Telnet entry except using the Dropbear command used by KOReader (according to ps ax):



menu_item :main : Dropbear (toggle) :cmd_output :500:quiet :/usr/bin/pkill -f "dropbear"
chain_success:skip:5
chain_failure :cmd_spawn :quiet :/bin/mount -t devpts | /bin/grep -q /dev/pts || { /bin/mkdir -p /dev/pts && /bin/mount -t devpts devpts /dev/pts; }
chain_success :cmd_spawn :quiet :exec /mnt/onboard/.adds/koreader/dropbear -E -R -p2222 -P /tmp/dropbear_koreader.pid
chain_success :dbg_toast :Started Dropbear server on port 2222
chain_failure :dbg_toast :Error starting Dropbear server on port 2222
chain_always:skip:-1
chain_success :dbg_toast :Stopped Dropbox server on port 2222

Last edited by elinkser; 05-04-2023 at 09:46 PM.
elinkser is offline   Reply With Quote