Firmware 4.42.23296

[JSWolf]

Originally Posted by Haesslich

That's a P265, instead of the N for Netronix.

That's P365.

[Haesslich]

Originally Posted by JSWolf

That's P365.

Shows how bad my memory's getting.

[atomicgeek5000]

Originally Posted by Marek

You can now start an ssh server by simply creating

/mnt/onboard/.kobo/ssh-enabled

and deleting

/mnt/onboard/.kobo/ssh-disabled

(assuming it exists) then reboot (this info should be written in the ssh-disabled file)

Spoiler:

unfortunately i havent been able to crack any of the passwords from the new per-device passwd files (maybe im doing something wrong?) and the admin:admin user seems to be gone.

EDIT: the ssh server will ask you to set a password on first connection to the root user im just blind

Is there a way to access this without telnet access? I had to do a factory reset and I haven't been able to find a usr/password combo that works with telnet anymore. Apologies if I'm missing something extremely obvious.

[PeterT]

Just curious if anyone has managed to used ssh to access their Kobo.

There is now a file in the .Kobo directory called (by default) ssh-disabled which contains

To enable ssh:
- Rename this file to ssh-enabled
- Reboot the device
- Connect via: ssh root@<device_ip>

I tried these steps and then tried to use ssh to access the Kobo. I was prompted to store an ssh key but then had no luck with the password prompt

I've a kludge via NickelMenu that lets me add a new ID to the Kobo with a known password and start telnet; this works but using that ID with ssh fails. (It's possible that one mistake I made here is that I only added my new ID to the passwd file, and NOT to the shadow file.)

I suppose I could try to change the root password on the Kobo to null (there is actually a script that the Kobo will run to set the password on first connection via ssh).

[PeterT]

Oh well! Just tried again; this time I had changed the root password to a known value from my kludge added admin id, and this time all worked!

[Aleron Ives]

How do you do any of this if telnet is disabled by default now and you need to rename a file in order to enable SSH? You would need SSH to enable SSH.

[PeterT]

No... the .kobo directory is exposed when you connect via USB.

[DNSB]

I simply set up a NickelMenu action to toggle SSH. Basically, if ssh-disabled is found, rename it to ssh-enabled and reboot, if ssh-enabled is found, rename it to ssh-disabled and reboot.

menu_item : main : Toggle SSH            : cmd_output     : 500: quiet: test -e /mnt/onboard/.kobo/ssh-disabled
      chain_failure  : skip              : 3
      chain_success  : cmd_spawn         : quiet  : mv /mnt/onboard/.kobo/ssh-disabled /mnt/onboard/.kobo/ssh-enabled
      chain_success  : dbg_toast         : SSH Disabled
      chain_always   : skip              : 2
      chain_failure  : cmd_spawn         : quiet  : mv /mnt/onboard/.kobo/ssh-enabled /mnt/onboard/.kobo/ssh-disabled
      chain_success  : dbg_toast         : SSH Enabled
      chain_always   :  power            : reboot

[DNSB]

Also, here's the item I use to display current SSH status.

#
menu_item :main : SSH (status)            : cmd_output     : 500: quiet: test -e /mnt/onboard/.kobo/ssh-disabled
      chain_success : dbg_toast           : SSH disabled on port 22
      chain_failure : dbg_toast           : SSH enabled on port 22
#

One oddity I noticed was that when I set the password on first login, it didn't seem to stick. After the 3rd login, I ran passwd and set the password and from there it seems to have stuck.

[stp]

Originally Posted by DNSB

I simply set up a NickelMenu action to toggle SSH. Basically, if ssh-disabled is found, rename it to ssh-enabled and reboot, if ssh-enabled is found, rename it to ssh-disabled and reboot.

menu_item : main : Toggle SSH            : cmd_output     : 500: quiet: test -e /mnt/onboard/.kobo/ssh-disabled
      chain_failure  : skip              : 3
      chain_success  : cmd_spawn         : quiet  : mv /mnt/onboard/.kobo/ssh-disabled /mnt/onboard/.kobo/ssh-enabled
      chain_success  : dbg_toast         : SSH Disabled
      chain_always   : skip              : 2
      chain_failure  : cmd_spawn         : quiet  : mv /mnt/onboard/.kobo/ssh-enabled /mnt/onboard/.kobo/ssh-disabled
      chain_success  : dbg_toast         : SSH Enabled
      chain_always   :  power            : reboot

DNSB,

Don't you have the dbg_toast messages swapped?

[DNSB]

Originally Posted by stp

DNSB,

Don't you have the dbg_toast messages swapped?

Yeah but since they don't show on the screen or show for so short a time they aren't readable, I haven't bothered to change them. That was why I did the SSH Status item.

[JennaMarie83]

Originally Posted by byrhias

I just checked and nope, ForceWiFi is off. I do use NickelMenu but ever since a couple months ago, the config for bluetooth/wifi no longer works on my NickelMenu. If I input the codes into the config file, I get a config error so I removed it and just turn on bluetooth/WiFi the old school way. Is there something wrong with the hardware of my device then? But I have no issues with 4.41. I'm stumped

I don't know if you already figured it out since posting this, but you just need to install the latest build of nickemenu:

https://github.com/RodrigoTomeES/Nic...ses/tag/v0.5.5

Won't fix the Wi-Fi bug you and I had on the latest firmware, but will get bluetooth commands working on nickelmenu.

[byrhias]

Originally Posted by JennaMarie83

I don't know if you already figured it out since posting this, but you just need to install the latest build of nickemenu:

https://github.com/RodrigoTomeES/Nic...ses/tag/v0.5.5

Won't fix the Wi-Fi bug you and I had on the latest firmware, but will get bluetooth commands working on nickelmenu.

Thank you!! Finally got it to work I must've installed the older version after my kobo factory reset itself.