PW4 developer.keystore update problems

[dhdurgee]

I attempted to apply the k5 update on my PW4 and am seeing problems.

I first copied it to the mounted root and after I ejected it safely I looked and found that "update your kindle" was still greyed out. Given this I tried with the ;log mrpi approach and nothing seemed to happen other than some screen corruption.

Given this I plugged back in and copied the k5 update to the mrpackages directory and then hit ;log mrpi again. That appeared to do something, but gave errors of some sort and then restarted my PW4.

The update may have worked, as KUAL opens.

Since restart my PW4 no longer mounts when I plug it in.

Checking USBNET status still shows USBMS active and SSH over WiFi as I had configured. I likewise can use kterm from KUAL if needed.

Unfortunately this is a new laptop and I don't have the public key SSH set up and would need my PW4 root password to get in that way.

How do I get this diagnosed and fixed?

Dave

Dave

[j.p.s]

If you saved your old ssh key pair someplace you can copy them to your new laptop.

[dhdurgee]

Originally Posted by j.p.s

If you saved your old ssh key pair someplace you can copy them to your new laptop.

The old laptop is still functional, although slow. Running Linux here, so where would it be stored? Perhaps in ~/.ssh? If not, where?

Dave

[j.p.s]

Yes, ~/.ssh
On the old laptop, assuming same username on both laptops, you can

cd
tar cf keys.tar .ssh
scp keys.tar newlaptop:

Or copy key.tar to the new laptop however you like.

On the new laptop

cd
mv .ssh .ssh.save
tar xf keys.tar

If for some reason you need to preserve the keys already on your new laptop and they have the same name, you need to rename one of the private/public pairs and do some homework on configuring to select which keys to use based on destination host.

I usually copy my existing keys when I get a new computer.

[dhdurgee]

I had already copied the .ssh directory, but that didn't do the trick.

I pulled my old laptop out of storage and confirmed it still worked, so I did a debug on it.

When I tried with the new laptop on debug I noticed immediately that there were differences in the default configurations. The old laptop shows "OpenSSH_8.2p1 Ubuntu-4ubuntu0.11, OpenSSL 1.1.1f 31 Mar 2020" while the new laptop shows "OpenSSH_9.6p1 Ubuntu-3ubuntu13.9, OpenSSL 3.0.13 30 Jan 2024" here.

Looking at the logs I noticed that the new default did NOT make use of ~/.ssh/known_hosts, so I had to add a configuration option to fix that. Unfortunately that is not the only configuration option I need to add.

Looking at the debug log on the new laptop I see:

debug2: pubkey_prepare: done
debug1: Offering public key: /home/dhdurgee/.ssh/id_rsa RSA SHA256:0o/HoAeI1TwYgP/toMixZt5VIoHV3D/foYcRHq/fJ0Q agent
debug1: send_pubkey_test: no mutual signature algorithm

So it appears I need to add a signature algorithm option here that is acceptable to dropbear. At this point I am lost.

I have attached the debug logs from both laptops in hope that someone here can tell me what configuration option needs to be added to get this working on the new laptop.

Thanks in advance for any assistance here.

Dave

PS: Grok to the rescue! I added PubkeyAcceptedAlgorithms +ssh-rsa to the config file.

[j.p.s]

I didn't know our configurations and use cases are so different.

I have never used dropbear on a kindle, nor ssh over wifi. I always set up openssh and as soon as it works with my keys I set networking over USB to be default and never enable USB mass storage again.

The newest openssh on any of my computers is OpenSSH_8.9p1

So I don't think I am in a position to help any more with this.

[dhdurgee]

Originally Posted by j.p.s

I didn't know our configurations and use cases are so different.

I have never used dropbear on a kindle, nor ssh over wifi. I always set up openssh and as soon as it works with my keys I set networking over USB to be default and never enable USB mass storage again.

The newest openssh on any of my computers is OpenSSH_8.9p1

So I don't think I am in a position to help any more with this.

No problem. I have now sorted out my problems. The one that caused me to open this thread turns out to have been coincidental.

I guess you must not use Calibre as I do to side load books with the PW4 plugged in.

Using Grok to find the solution for my ssh configuration issue was useful, as I had not attempted such a detailed issue solution in that manner before. I'm sure that someone here would have given me an answer eventually, but Grok provided it in seconds.

Thanks again for your help.

Dave

[estral]

Since your Kindle isn’t mounting now, the issue might be related to the update corrupting the USB settings. You could try force restarting your device by holding the power button for 40 seconds to reset everything. If SSH is still working over WiFi, you could try re-adding the USB gadget driver or reconfiguring it via the terminal. As a last resort, you might want to do a hard reset or even restore the Kindle to factory settings to fix the USB mounting issue.

[dhdurgee]

Originally Posted by estral

Since your Kindle isn’t mounting now, the issue might be related to the update corrupting the USB settings. You could try force restarting your device by holding the power button for 40 seconds to reset everything. If SSH is still working over WiFi, you could try re-adding the USB gadget driver or reconfiguring it via the terminal. As a last resort, you might want to do a hard reset or even restore the Kindle to factory settings to fix the USB mounting issue.

As noted in the above post, the mounting issue was coincidental. See separate post for details.

Dave