Hi, great project - thank you.
I noticed that the image files you are distributing (usb4vc_rpi_img_0.3.3.img for example) are just a clone of your local system. This includes passwords, an authorized_keys file that allows you to remotely access the pi user, a static set of SSH keys that are now identical across everyone else's use of this image, etc. Ideally - we would want to "reset" the system so the machine-id, ssh keys, and so forth are all cleaned before others download it.
I created a script that does this, please find it attached. You can just run it on your existing image like this (prior to distribution):
./reset-pi-image.sh usb4vc_rpi_img_0.3.3.img
reset-pi-image.sh
Hi, great project - thank you.
I noticed that the image files you are distributing (usb4vc_rpi_img_0.3.3.img for example) are just a clone of your local system. This includes passwords, an authorized_keys file that allows you to remotely access the pi user, a static set of SSH keys that are now identical across everyone else's use of this image, etc. Ideally - we would want to "reset" the system so the machine-id, ssh keys, and so forth are all cleaned before others download it.
I created a script that does this, please find it attached. You can just run it on your existing image like this (prior to distribution):
./reset-pi-image.sh usb4vc_rpi_img_0.3.3.img
reset-pi-image.sh