In trying to set up wifi usb connection, I can no longer connect to Scribe at all :(

[arooni]

I was doing so well too!

I could previously ssh via:

ssh root@192.168.15.244 -vvv

But I was trying to set up ssh connection via wifi. So I clicked "Open SSH". I thought I had set up the keys correctly, but apparently I had not. When I could still could connect, I created a ~/.ssh and ~/.authorized_keys file and added some public keys.

I now realize this was a terrible mistake.

Now I can no longer connect via ssh root@192.168.15.244 -vvv, as it prompts me for a password, and I hit enter, and I see

Welcome to Kindle!

debug3: receive packet: type 51
debug1: Authentications that can continue: publickey,password
debug3: start over, passed a different list publickey,password
debug3: preferred publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Offering public key: /Users/david/.ssh/id_rsa RSA SHA256:j/LJr/t3s0BEBg0EfDqnymeVeb3++g+Y/n3TTEeqfhg
debug3: send packet: type 50
debug2: we sent a publickey packet, wait for reply
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey,password
debug1: Trying private key: /Users/david/.ssh/id_ecdsa
debug3: no such identity: /Users/david/.ssh/id_ecdsa: No such file or directory
debug1: Trying private key: /Users/david/.ssh/id_ecdsa_sk
debug3: no such identity: /Users/david/.ssh/id_ecdsa_sk: No such file or directory
debug1: Offering public key: /Users/david/.ssh/id_ed25519 ED25519 SHA256:0+9DWNocSCfBVtjcjkx3TiRLYgl35DrT5iDBbbC55uU
debug3: send packet: type 50
debug2: we sent a publickey packet, wait for reply
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey,password
debug1: Trying private key: /Users/david/.ssh/id_ed25519_sk
debug3: no such identity: /Users/david/.ssh/id_ed25519_sk: No such file or directory
debug1: Trying private key: /Users/david/.ssh/id_xmss
debug3: no such identity: /Users/david/.ssh/id_xmss: No such file or directory
debug1: Trying private key: /Users/david/.ssh/id_dsa
debug3: no such identity: /Users/david/.ssh/id_dsa: No such file or directory
debug2: we did not send a packet, disable method
debug3: authmethod_lookup password
debug3: remaining preferred: ,password
debug3: authmethod_is_enabled password
debug1: Next authentication method: password
root@192.168.15.244's password:

So I think I locked myself out of the kindle via ssh or usbnetwork? Would reinstalling it help?

I'm so sad, I was doing so great! ;(

since kual and mrpi are still installed; anyway to write a script that fixes it and install as mrpi package?

[NiLuJe]

Originally Posted by NiLuJe

3. Setup key pair auth before you tweak any USBNet settings.

Originally Posted by "README_FIRST.txt

Shared key auth support. Store your public keys in usbnet/etc/authorized_keys (OpenSSH format).

Disable OpenSSH (& SSH over Wi-Fi), because either of them disable the passwordless auth hacks.

[arooni]

If I see "SSHD: Use OpenSSH" on usbnetwork, I should select that option so it'll default to dropbear?

Also, your readme states: "The pubkeys are stored, in OpenSSH format, in usbnet/etc/authorized_keys (i.e., the very same file that's usually found as ~/.ssh/authorized_keys on real *nix OpenSSH setups)."

Yet there is no authorized_keys file in the [kindleroot]/usbnet/etc/ ; I assume I am to create one?

I assume all the keys that make ssh'ing over USB won't be messed up by me creating an authorized_keys file?

[mergen3107]

These are action items, not status. So if you hit it, it will switch to OpenSSH, meaning that now it is dropbear.

[arooni]

I don't see an authorized_keys directory where I think there should be one?

[root@kindle etc]# pwd
/mnt/us/usbnet/etc
[root@kindle etc]# ls -l
total 808
-rwxrwxrwx 1 root root 81 Dec 16 21:41 TURN_ON_NETWORKING_COMMAND
-rwxrwxrwx 1 root root 39 Nov 6 11:17 VERSION
-rwxrwxrwx 1 root root 1334 Dec 17 21:23 config
-rwxrwxrwx 1 root root 1334 Dec 16 21:40 config.default
drwxrwxrwx 2 root root 8192 Oct 30 20:30 dot.lftp
drwxrwxrwx 2 root root 8192 Oct 30 20:30 dot.ssh
-rwxrwxrwx 1 root root 457 Oct 30 20:30 dropbear_dss_host_key
-rwxrwxrwx 1 root root 141 Oct 30 20:30 dropbear_ecdsa_host_key
-rwxrwxrwx 1 root root 83 Oct 30 20:30 dropbear_ed25519_host_key
-rwxrwxrwx 1 root root 805 Oct 30 20:30 dropbear_rsa_host_key
-rwxrwxrwx 1 root root 1054 Oct 30 20:30 htoprc
-rwxrwxrwx 1 root root 2163 Oct 30 20:30 inputrc
drwxrwxrwx 2 root root 8192 Dec 16 21:40 lftp
drwxrwxrwx 2 root root 8192 Dec 16 21:40 ltrace
-rwxrwxrwx 1 root root 578094 Oct 30 20:30 moduli
drwxrwxrwx 2 root root 8192 Dec 16 21:40 nano
-rwxrwxrwx 1 root root 10726 Oct 30 20:30 nanorc
-rwxrwxrwx 1 root root 1893 Oct 30 20:30 ssh_config
-rwxrwxrwx 1 root root 1385 Oct 30 20:30 ssh_host_dsa_key
-rwxrwxrwx 1 root root 604 Oct 30 20:30 ssh_host_dsa_key.pub
-rwxrwxrwx 1 root root 505 Oct 30 20:30 ssh_host_ecdsa_key
-rwxrwxrwx 1 root root 176 Oct 30 20:30 ssh_host_ecdsa_key.pub
-rwxrwxrwx 1 root root 411 Oct 30 20:30 ssh_host_ed25519_key
-rwxrwxrwx 1 root root 96 Oct 30 20:30 ssh_host_ed25519_key.pub
-rwxrwxrwx 1 root root 2602 Oct 30 20:30 ssh_host_rsa_key
-rwxrwxrwx 1 root root 568 Oct 30 20:30 ssh_host_rsa_key.pub
-rwxrwxrwx 1 root root 3531 Oct 30 20:30 sshd_config
drwxrwxrwx 17 root root 8192 Dec 16 21:40 terminfo
-rwxrwxrwx 1 root root 3088 Oct 30 20:30 tmux.conf
drwxrwxrwx 3 root root 8192 Dec 16 21:40 zsh
[root@kindle etc]#

[mergen3107]

It is not a directory, but a file without extension and most importantly LF line ending (UNIX).

[arooni]

Would copying the file from one of my mac computers be sufficient?

EDIT: Fixed it all; can connect via WIFI now without issue. Copied the authorized_keys file over in USB mass storage mode as indicated in the README FIRST. I assumed I knew what I was doing by trying to create a .ssh folder in the root of the kindle; but that was a mistake. There's some magic that I don't pretend to understand with usbnet that makes ssh to the kindle possible.

Much easier to fiddle about with koreader this way :P

Still not sure if it's safe to leave the wifi on at boot even though that's most convenient.