Jarrod Johnson 6eb4bf28e5 Another iteration to try to have IP adaptive syncfiles ... It is likely that a client connects from fe80::, which is explicitly omitted from ssh principals. This time, have the client provide all currently set IP addresses and the server will make a determination. There remains the possibility it misconfigures a nic and tries to use that, inducing failure. One strategy would be to filter the addresses and only provide from the 'current' interface. Another is to just take the hit as the node is likely going to suffer a lot from such a misconfiguration anyway.		2022-10-05 12:23:47 -04:00
..
firstboot.d	Add more to the SUSE profiles	2022-08-24 16:07:38 -04:00
post.d	Add more to the SUSE profiles	2022-08-24 16:07:38 -04:00
pre.d	Add more to the SUSE profiles	2022-08-24 16:07:38 -04:00
firstboot.custom
firstboot.sh	Have suse give up after a minute	2022-09-27 08:33:00 -04:00
functions
getinstalldisk	Sync up getinstalldisk and add another m.2 model	2022-09-01 13:22:50 -04:00
post.custom
post.sh
pre.sh	Ensure early existance of ca.pem	2022-08-25 16:45:00 -04:00
prechroot.sh
setupssh.sh
syncfileclient	Another iteration to try to have IP adaptive syncfiles	2022-10-05 12:23:47 -04:00