Support for rpi-imager: Selection of DietPi

[StephanStS]

Needed for rpi-imager integration:

• DietPi logo
• .json file (testwise extended, needs to be reduced later). File can be renamed to dietpi_list.json

To request DietPi to be integrated into rpi-imager OS list, these files need to be supplied.

Local usage (with extended .json file): rpi-imager --repo custom_os_list.json

[MichaIng]

This is something to implement into rpi-imager itself, instead of in DietPi, isn't it? Or what would be the reason someone adds a custom OS via custom JSON and load it via console with rpi-imager, instead of just downloading and flashing the DietPi image directly?

Did you find the JSON in the source code? I could find the docs only 🤔: https://github.com/raspberrypi/rpi-imager/blob/qml/doc/json-schema/os-list-schema.json
Is it entirely hosted on a server outside of the source code repository? You mentioned there is a web mask to request adding a new OS to the RPi imager. Can you post the link?

[StephanStS]

This is something to implement into rpi-imager itself, instead of in DietPi, isn't it? Or what would be the reason someone adds a custom OS via custom JSON and load it via console with rpi-imager, instead of just downloading and flashing the DietPi image directly?

Did you find the JSON in the source code? I could find the docs only 🤔: https://github.com/raspberrypi/rpi-imager/blob/qml/doc/json-schema/os-list-schema.json Is it entirely hosted on a server outside of the source code repository? You mentioned there is a web mask to request adding a new OS to the RPi imager. Can you post the link?

It's there: https://forms.gle/cbsU27aLLVaxUXbw8
See also: raspberrypi/rpi-imager#545

I think there are these options:

• Add RPI images via form (given above) to rpi-imager
• Generate an own .json which also supports other hardware variants we support and somehow spread it via DietPi
• Do both

[MichaIng]

I filled the form. @lurch if I may:

• DietPi ships with a default password.
• It can be changed during early boot stage (before network and login prompts) via dietpi.txt file on the FAT/boot partition.
• With the same config file, an SSH pubkey can be provided, and SSH password login for root or all users can be disabled, which is as well applied during early boot stage, before network and SSH server are started.
• On first login, users are further presented a dialogue to change the password.
• Right now, No/ESC can be selected to skip changing the default password. But we could make it mandatory.

[lurch]

@lurch if I may:

Again, these are all questions for @tdewey-rpi rather then myself. I believe the problem with leaving a default password enabled is that it leaves your OS vulnerable to botnet attacks.

[tdewey-rpi]

@lurch is again correct - I'm the effective curator of the OS list.

Right now, No/ESC can be selected to skip changing the default password. But we could make it mandatory.

I'm not entirely comfortable with that posture. In such a case, users of Raspberry Pi Imager could be inadvertently creating botnet nodes by selecting DietPi and making choices that wouldn't necessarily be obviously poor. If you are prepared to accommodate the change mandating the user set an authentication credential of their choice, I would be minded to accept the DietPi posture on this question.

[MichaIng]

Okay, I'll make the password change mandatory on first login, with next DietPi release, planned for Mai 17th.