K3 My Route to Root

[AwedJob]

A simple thread to chronicle my adventures in gaining root access to my K3W.

On My K3W:

• jailbreak
• ss
• mkk
• KUAL
• gawk
• helper
• lpad
• usbNetwork
• mrinstaller

Progress:

• added grayscale PNGs for screensavers
• Manual IPV4 IP 192.168.2.1
• ping'd the K3W from Mac OS X, 192.168.2.2
• ssh 192.168.2.2 failed multiple attempts
• paired key set up & ssh root@192.168.2.2 yields

  Welcome to Kindle!

  then fails
• Obtained root PW and recovery PW via kindletool

I'm very happy with my progress. I spend a couple of hours on it each night after work. I am currently stumped as to why I can't gain ssh access via the usbNetwork connection. I have generated and deleted and regenerated key pairs many times on both Linux and OS X systems to ssh into the K3W.

I can ssh from my Mac to my Linux box and vice versa. I have disabled the Network Manager in Linux and modified the sshd_config file on the Mac. My guess is that I am missing some small yet important step that is making this part get fubar'd.

[knc1]

If your list is complete, then one of the things you are missing is the installation of a "customer firmware build".
None of our add-ins (other than the jb and hotfix) are intended to be run on the "factory only firmware build".

[NiLuJe]

@knc1: It's a K3 .

@AwedJob: Define "fails". (You can also check what happens behind the scenes w/ ssh -vvv user@host).

[AwedJob]

Originally Posted by knc1

If your list is complete, then one of the things you are missing is the installation of a "customer firmware build".
None of our add-ins (other than the jb and hotfix) are intended to be run on the "factory only firmware build".

Thanks for the information. I'll get right on that.

I am happy to report a successful ssh via usbNetwork. Woot!

[AwedJob]

Originally Posted by NiLuJe

@knc1: It's a K3 .

@AwedJob: Define "fails". (You can also check what happens behind the scenes w/ ssh -vvv user@host).

Whenever I tried to do a simple ssh, I received a "Permission denied" message.
------------------------------------
Dryad:~ Scott$ ssh 192.168.2.2

Welcome to Kindle!

Scott@192.168.2.2's password:
Permission denied, please try again.
-------------------------------------

This morning I used KUAL to "Restore default config" and tried again. I was able to ssh in using root@192.168.2.2 and the password for the paired key set up. Here's the result of your suggested command:

-------------------------------------
[root@kindle root]# ssh -vvv user@host
OpenSSH_7.0p1, OpenSSL 0.9.8zg 11 Jun 2015
debug1: Reading configuration data /mnt/us/usbnet/etc/ssh_config
ssh: Could not resolve hostname host: Temporary failure in name resolution
-------------------------------------

Thank you.

[j.p.s]

Unless you have added a user Scott to your Kindle and have a hostname host with IP 192.168.2.2 in a hosts file on your PC, it should be

ssh root@192.168.2.2

[NiLuJe]

Yeah, user@host was meant as a placeholder (might not have been very clear, because I was on my phone ).

I basically meant "stick a -vvv somewhere on your commandline" to enable verbose debug.

I can definitely confirm that you shouldn't need to touch a config *anywhere* to have it work, and that in fact I actively discourage doing this unless you know what you're doing, which might explain why the KUAL reset fixed it ;p.

[AwedJob]

Originally Posted by knc1

If your list is complete, then one of the things you are missing is the installation of a "customer firmware build".
None of our add-ins (other than the jb and hotfix) are intended to be run on the "factory only firmware build".

@knc1 - My K3W firmware version is 3.4. I assume this is what you mean by "customer firmware build" since my device is not currently using the 3.1 fw version.

It's been a few years since I've been active on a forum like this and I can't seem to remember how to edit my original post to reflect that. I'll figure it out and edit the post when I do.

[knc1]

Originally Posted by AwedJob

@knc1 - My K3W firmware version is 3.4. I assume this is what you mean by "customer firmware build" since my device is not currently using the 3.1 fw version.

It's been a few years since I've been active on a forum like this and I can't seem to remember how to edit my original post to reflect that. I'll figure it out and edit the post when I do.

Doesn't matter, I was wrong when you wrote that you are using a K3.
I misunderstood the model you were writing about.
tl;dr: My bad.


(NiLuJe already woke me up about it being a K3 - see above).

[AwedJob]

Happily poking around in my K3W via ssh. Today I attempted to ssh via WiFi. I edited the file /mnt/us/usbnet/etc/config as follows...
True:
K3_WIFI, K3_WIFI_SSHD_ONLY, & USE_OPENSSH
False:
USE_VOLUMD, QUIET_DROPBEAR, & TWEAK_MAC_ADDRESS

I configured my router (apple AE) to bind ("DHCP only") the K3W MAC address to the ip 192.168.0.22 via DHCP Reservations. Both ping and arp returned packet information from the K3W. Attempting to ssh via the WiFi ip in debug mode gives me the following:

-------------------------------------
Dryad:~ Scott$ ssh -vvv root@192.168.0.22
OpenSSH_7.9p1, LibreSSL 2.7.3
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 48: Applying options for *
debug1: /etc/ssh/ssh_config line 52: Applying options for *
debug2: resolve_canonicalize: hostname 192.168.0.22 is address
debug2: ssh_connect_direct
debug1: Connecting to 192.168.0.22 [192.168.0.22] port 22.
debug1: connect to address 192.168.0.22 port 22: Operation timed out
ssh: connect to host 192.168.0.22 port 22: Operation timed out
-------------------------------------

I could not find an ssh_config file in a /etc/ssh/ directory. In the /etc/ directory I did find an ssh_config file and the lines mentioned in the debug message are listed below:
48 # TunnelDevice any:any
52 # RekeyLimit 1G 1h

While I am attempting the WiFi ssh I also have the k3w plugged in to the usb cable. I have tried wifi ssh plugged and unplugged and while plugged; with an ssh connection via usbnetwork and without.

I also tried DHCP and NAT router mode and was able to arp and ping but received the same debug response as above.
-------------------------------------
Dryad:~ Scott$ ssh -vvv root@10.0.1.2
OpenSSH_7.9p1, LibreSSL 2.7.3
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 48: Applying options for *
debug1: /etc/ssh/ssh_config line 52: Applying options for *
debug2: resolve_canonicalize: hostname 10.0.1.2 is address
debug2: ssh_connect_direct
debug1: Connecting to 10.0.1.2 [10.0.1.2] port 22.
debug1: connect to address 10.0.1.2 port 22: Operation timed out
ssh: connect to host 10.0.1.2 port 22: Operation timed out
-------------------------------------

Now it's time for dinner and a walk with my pup cuz it's so amazingly beautiful outside.

[DeKuns]

All you are very advanced.

I am eyeing now Kindle Keyboard 3G + Wifi as well after learning that it has many tempting characteristics:
still has a built-in speaker and headphone jack, TTS, and limited free 3G that can still access (some) https website including gmail. The second market price is good enough.

If I need bluetooth and screen light, then Chinese manufacturers has all add-on for these for bellow US$10 in total. Time hunt one.

[NiLuJe]

@AwedJob:

K3_WIFI_SSHD_ONLY does what it says on the tin. So of course USBNet is no more with that enabled.

Speaking of, switching to SSHD only may require either a full reboot, or a couple toggle to take, because reasons. I generally don't recommend it.