When storing your keys not in rootfs but on a separate data partition (using symbolic links or overlay fs), keys are overwritten on each firmware upgrade which lets rc-once run again (which happens when using opkg upgrade/update or RAUC in an A/B scheme for example).
Changing keys are at best annoying, but may be interpreted as an attack as well. Note: if an empty or invalid key is found, the key is still regenerated. Signed-off-by: Alexander Dahl <[email protected]> --- Notes: v1 (RFC) --> v2 --------------- - Improve check and look at size and if it's a valid key (Michael Olbrich) - Reword commit message (swap prefix, adapt reasoning) projectroot/etc/rc.once.d/openssh | 1 + 1 file changed, 1 insertion(+) diff --git a/projectroot/etc/rc.once.d/openssh b/projectroot/etc/rc.once.d/openssh index 545586f07..717d6457e 100644 --- a/projectroot/etc/rc.once.d/openssh +++ b/projectroot/etc/rc.once.d/openssh @@ -27,6 +27,7 @@ create_keys() { hostkeys="$(get_hostkeys)" || return for keyfile in $hostkeys; do + [ -s "$keyfile" ] && ssh-keygen -l -f "${keyfile}.pub" > /dev/null && continue create_key "$keyfile" || return done } -- 2.30.2 _______________________________________________ ptxdist mailing list [email protected] To unsubscribe, send a mail with subject "unsubscribe" to [email protected]
