Go to file
Dustin 8933e517fb fedora-common: Do not configure SSH host cert
When the SSH daemon is already configured to use an SSH host
certificate but the specified certificate file does not exist, then the
server will not try to use it later once it is created.  This
essentially means that the certificate obtained during first boot will
not be used untile the SSH daemon is restarted.

Rather than try to set all of this up in the kickstart, it's probably
better to just let Ansible do it.  Then, the SSH daemon can be restarted
as needed automatically (by the host provisioner).
2025-05-09 20:49:02 -05:00
autoprovision.ks autoprovision: Trigger host online webhook 2025-02-08 17:22:44 -06:00
burp1.ks Add kickstart for burp1 2020-01-25 10:13:40 -06:00
centos7.ks Add generic CentOS 7 kickstart 2018-08-31 20:15:08 -05:00
centos8.ks Add generic CentOS 8 kickstart 2019-09-24 16:19:49 -05:00
dc1.ks Add kickstart for dc1 2019-03-22 09:08:19 -05:00
dns0.ks Add kickstart for dns0 2018-02-19 23:18:17 -06:00
fedora-common.ks fedora-common: Do not configure SSH host cert 2025-05-09 20:49:02 -05:00
fedora-disk-dch.ks fedora-disk-dch: Add back /boot partition 2025-03-04 19:33:49 -06:00
fedora-rpi-common.ks fedora-disk-dch: Add back /boot partition 2025-03-04 19:33:49 -06:00
fedora-rpi-nvme-noswap.ks fedora-disk-dch: Factor out disk layout 2025-01-30 16:47:08 -06:00
fedora-rpi-nvme.ks fedora-rpi: Split eMMC vs NVMe config 2024-12-28 17:23:17 -06:00
fedora-rpi.ks fedora-rpi: Enable auto provisioning 2025-02-23 16:09:37 -06:00
fedora.ks autoprovision: Trigger host online webhook 2025-02-08 17:22:44 -06:00
gw0.ks Add kickstart for gw0 2018-05-04 20:46:41 -05:00
gw1.ks Add kickstart for gw1 2021-05-29 10:04:14 -05:00
toad.ks Add kickstart for toad 2018-07-28 10:33:52 -05:00
vmhost0.ks vmhost0: Update to Fedora 32 2021-10-09 10:29:59 -05:00
vmhost1.ks Add kickstart for vmhost1 2019-04-26 15:21:05 -05:00
zaphym.ks Add kickstart for zaphym 2020-05-03 14:57:25 -05:00