Quote:
Originally Posted by NiLuJe
@PoP: That usually means wrong arch.
Try this (untested, I just didn't have anything better to do  ).
You'll probably have to call an SSH client or a patched busybox login applet, unless you know your root password. And disable SSL, it seems sligtly broken, and will call openssl to generate a cert, which will probably take forever on the Kindle HW.
And, if it even works, you probably won't be able to do much, because I assume it expects a full 105 keys keyboard ;o). |
OK I have the root password... trying... lots of fun playing with openssl... trying... now disabling SSL... trying more with debug:
Code:
[root@kindle shellinabox]# ./shellinaboxd --disable-ssl -b -d
Command line: ./shellinaboxd --disable-ssl -b -d
Substituting "nobody's" primary group for "nogroup"
Listening on port 4200
Substituting "nobody's" primary group for "nogroup"
Connecting to the url:
Oops process terminated:
Code:
[root@kindle shellinabox]# Accepted connection from localhost:32882
Handling "GET" "/"
localhost - - [19/Mar/2011:11:26:46 -0400] "GET / HTTP/1.1" 200 4967
Handling "GET" "/styles.css"
localhost - - [19/Mar/2011:11:26:47 -0400] "GET /styles.css HTTP/1.1" 200 7315
Handling "GET" "/ShellInABox.js"
localhost - - [19/Mar/2011:11:26:47 -0400] "GET /ShellInABox.js HTTP/1.1" 200 186894
Handling "GET" "/keyboard.html"
localhost - - [19/Mar/2011:11:26:49 -0400] "GET /keyboard.html HTTP/1.1" 200 3181
Handling "POST" "/?"
Check failed at shellinabox/session.c:173 in newSessionKey(): (fd = NOINTR(open("/dev/urandom", O_RDONLY))) >= 0
Uh-oh. Dreaded keyboard? To be continued.