new image 8.3.x using an older backup/restore

[Tim Curtis]

I think I've probably glossed over too many details with regard to the new security setup since 8.3.0, and what implications there may or may not be when restoring from an older backup. 

The sole reason why I've ever really needed to use the back/restore function is to preserve numerous custom internet radio stations. All other configuration steps take me literally 1 minute, no sweat, I don't actually need to use a backup for that, but the custom internet radio stations would take forever, and thus I've used backup/restore ever since the radio station manager was changed some versions ago whereby there is no longer a separate radio station only backup/restore tool or procedure.

I had numerous problems with the recent Moode updates resulting in a bricked system, both in-place updates to existing working images, and new images written using the Raspberry Pi Imager tool, using with the media player OS option, or using an image downloaded to my computer.

Somehow my last attempt using Balena Etcher in writing a new image, then having the ability to boot that image and enter the System config to apply an older backup and restore my settings and radio stations actually worked, and resulted in a working 8.3.2 on a new 8GB v1.5 board. All other previous attempts using that same board and same new microSD card had failed. I can enable SSH on that instance after restoring the backup, however the old userid and password are rejected.

So my question is this: If in a previous backup SSH was set to disabled, and there had been no previous attempt in that instance to change the userid or password, if I then apply that backup to a newly written 8.3.x image, will my userid and password remain the old and now considered no longer secure combination from 8.2.x and prior?

If yes to the above, I can still restore from that backup, and then just use the instructions for how to change the userid and password on Existing Installations, i.e. sudo rename-user?

On a Lite image such as Moode, I can use sudo rename-user via SSH?

Or is there a better way to utilize an older backup that was configured for SSH disabled, with no change to the userid or password, and a new 8.3.x image?

The goal is to preserve and restore a ton of custom internet radio stations contained in the backup, while adhering to the new security setup.

SSH service and OS userid/password are strictly outside and independent of moOde Backup/Restore feature. If your Restore to 832 is not working then troubleshooting will be needed.

Also, if the Raspberry Pi Imager method of prepping a new image with SSH and userid/password etc is not working according to the Setup guide then I'll need some help in trying to create a failure repro because on my end it's working perfectly.

Just be aware that I'm limited to using MacOS for the Pi Imager. If the Pi Imager app is not working correctly on Windows or Linux desktops then another dev with those OS's will need to help troubleshoot.