Does exist a SSH Help Tool?

[jmesar]

My Question is if on Kindle exist any way to monitor, or to see a log of the SSH activity?

On ;dumpMessages I did not see anything seemingly related.

I have fail to get acces to Kindle Shell:

. 2012-04-13 10:10:00.625 WinSCP Version 4.3.6 (Build 1655) (OS 5.1.2600 Service Pack 3)
. 2012-04-13 10:10:00.625 Configuration: HKEY_CURRENT_USER\Software\Martin Prikryl\WinSCP 2\
. 2012-04-13 10:10:00.625 Local account: FANGORN\jmesar
. 2012-04-13 10:10:00.640 Login time: Viernes, 13 de Abril de 2012 10:10:00 a.m.
. 2012-04-13 10:10:00.640 --------------------------------------------------------------------------
. 2012-04-13 10:10:00.640 Session name: 192.168.2.2 (Modified stored session)
. 2012-04-13 10:10:00.640 Host name: 192.168.2.2 (Port: 22)
. 2012-04-13 10:10:00.640 User name: (Password: No, Key file: Yes)
. 2012-04-13 10:10:00.640 Tunnel: No
. 2012-04-13 10:10:00.640 Transfer Protocol: SFTP (SCP)
. 2012-04-13 10:10:00.640 Ping type: -, Ping interval: 30 sec; Timeout: 15 sec
. 2012-04-13 10:10:00.640 Proxy: none
. 2012-04-13 10:10:00.640 SSH protocol version: 2; Compression: No
. 2012-04-13 10:10:00.640 Bypass authentication: No
. 2012-04-13 10:10:00.640 Try agent: Yes; Agent forwarding: No; TIS/CryptoCard: No; KI: Yes; GSSAPI: No
. 2012-04-13 10:10:00.640 Ciphers: aes,blowfish,3des,WARN,arcfour,des; Ssh2DES: No
. 2012-04-13 10:10:00.640 SSH Bugs: -,-,-,-,-,-,-,-,-
. 2012-04-13 10:10:00.640 SFTP Bugs: -,-
. 2012-04-13 10:10:00.640 Return code variable: Autodetect; Lookup user groups: Yes
. 2012-04-13 10:10:00.640 Shell: default
. 2012-04-13 10:10:00.640 EOL: 0, UTF: 2
. 2012-04-13 10:10:00.640 Clear aliases: Yes, Unset nat.vars: Yes, Resolve symlinks: Yes
. 2012-04-13 10:10:00.640 LS: ls -la, Ign LS warn: Yes, Scp1 Comp: No
. 2012-04-13 10:10:00.640 Local directory: default, Remote directory: home, Update: No, Cache: Yes
. 2012-04-13 10:10:00.640 Cache directory changes: Yes, Permanent: Yes
. 2012-04-13 10:10:00.640 DST mode: 1
. 2012-04-13 10:10:00.640 --------------------------------------------------------------------------
. 2012-04-13 10:10:00.671 Looking up host "192.168.2.2"
. 2012-04-13 10:10:00.671 Connecting to 192.168.2.2 port 22
. 2012-04-13 10:10:01.625 Failed to connect to 192.168.2.2: Network error: Connection refused
* 2012-04-13 10:10:01.640 (ESshFatal) Network error: Connection refused.


Jail Break OK, SS ok, USBnetwor OK, but no Kindle not answer…
I know usbnetwork hack is OK because accessing usb by cable the Ethernet RNDIS Windows show connection ok.
I follow the instruction of exxyea (https://www.mobileread.com/forums/showpost.php?p=1701844&postcount=6):

3. Prepare for SSH Key Access
1. Connect your Kindle. There should now be a usbnet folder in your root directory.
2. Go to usbnet\etc\.
3. In the etc folder, open and edit the config file with a Notepad. Change these parts to:
K3_WIFI="true"
K3_WIFI_SSHD_ONLY="true"
4. Open PuTTYgen, the key generator.
5. With SSH-2 RSA selected, click Generate. Move your mouse around the blank area to generate a code.
6. Make and confirm a passphrase.
7. Click Save public key to your computer as the file "authorized_keys" with no extension. You can also copy the generated code yourself, paste it to a Notepad, save, and then change the extension from ".txt" to no extension.
8. Click Save private key to your computer as any file name with the extension ".ppk".
9. Copy your "authorized_keys" file from your computer to your Kindle under usbnet\etc\.
10. Disconnect your Kindle.
11. Make sure your Kindle's Wifi is turned on and you are connected to a network. (You should also be registered or else you'll have to .)
12. In the Home page on your Kindle, press Del and then type these lines one after the other:
;debugOn
~usbNetwork
;debugOff
13. Open up PuTTY for shell access.
14. Put in your Kindle's IP Address under Session.
- The simplest way to view your Kindle's IP address is to go to the Settings page (click Menu -> Settings). Once there, hold down ALT and press UGG (711) to get to the 711 page.
14. On the left sidebar, go to Connections -> SSH -> Auth. In the box under Private key for authentication, select your saved private key file (the one with the extension ".ppk")
15. Click Open.


4. Run Commands
A black window should pop up once you connect. If you get network error: connection refused, I would reconnect my Kindle and regenerate some new keys.
1. When login appears, type "root".

I try several times creating different authorized_keys but the same….

[knc1]

Try adding the debug flag(s) to your ssh command.

If using the command line, then: ssh -vv <whatever>
If using Putty, then Putty should have a debug flag(s) option somewhere.

The "connection refused" is a general purpose result message, designed not to give away the reason for the failure.
Most often the cause is the sshd daemon isn't running on the target device or port 22 is firewalled somewhere.

Changing keys will not solve this, it is failing long before any keys become involved in the handshake process.

The "normal" (meaning, a standard Linux or *nix installation) location for the connection log messages is /var/log/auth.log but I do not know if your Kindle uses that "normal" name and path for the log.

[jmesar]

I made a stupid error configuration the usbNetwork, a “topological” error; the usb cable have two ends, so, two IP address, one at Kindle and other at the PC, I forgot to adjust the ip in the PC.