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
infiniband
post.d
pre.d
add_local_repositories	Switch to importlib for newer python	2022-06-07 10:35:08 -04:00
configbmc	Correct configbmc misidentification of lan chan	2022-01-10 09:29:40 -05:00
firstboot.custom
firstboot.service
firstboot.sh	Do not tail old content from firstboot	2022-07-18 09:35:40 -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	Tighter permissions on /var/log/confluent	2021-12-08 07:42:19 -05:00
pre.custom
pre.sh	Adjust to correct ntp for 9 and up	2022-06-17 09:06:33 -04:00
prechroot.sh	Appl consistent name to apiclient for EL8	2022-04-13 11:27:30 -04:00
setupssh.sh
syncfileclient	Another iteration to try to have IP adaptive syncfiles	2022-10-05 12:23:47 -04:00
tpm_luks.sh