Age | Commit message (Collapse) | Author |
|
The shim review board (which is the secure boot base loader) recommends using
ephemeral keys when signing the Linux Kernel. This commit enables the Kernel
build system to generate a one-time ephemeral key that is used to:
* sign all build-in Kernel modules
* sign all other out-of-tree Kernel modules
The key lives in /tmp and is destroyed after the build container exits and is
named: "VyOS build time autogenerated kernel key".
In addition the Kernel now uses CONFIG_MODULE_SIG_FORCE. This now makes it
unable to load any Kernel Module to the image that is NOT signed by the
ephemeral key.
|
|
As the VyOS Linux Kernel will be compiled with CONFIG_MODULE_SIG_FORCE all
driver modules need to be cryptographically signed. This happens during build
of the Kernel and it's 3rd party modules.
Stripping the objects would remove said signature and the system will be unable
to boot b/c of CONFIG_MODULE_SIG_FORCE.
|
|
This adds support for UEFI Secure Boot. It adds the missing pieces to the Linux
Kernel and enforces module signing. This results in an additional security
layer where untrusted (unsigned) Kernel modules can no longer be loaded into
the live system.
NOTE: This commit will not work unless signing keys are present. Arbitrary
keys can be generated using instructions found in:
data/live-build-config/includes.chroot/var/lib/shim-signed/mok/README.md
|
|
|
|
|
|
suricata: T751: Disable suricata.service by default
|
|
|
|
|
|
T6228: Cleanup of not existing systemd units
|
|
Delete not existing units:
```
06:12:51 Failed to disable unit, unit logd.service does not exist.
06:12:51 Failed to disable unit, unit heartbeat.service does not exist.
```
|
|
The builder log:
```
06:12:53 Failed to disable unit, unit vpp.service does not exist.
```
|
|
With libpam-systemd >= 230-2, ssh-session-cleanup.service is no longer
necessary because when `UsePAM yes` in `/etc/ssh/sshd_config` (which is
the default), SSH sessions are cleaned up automatically when ssh-server
is shutdown or the system is rebooted.
|
|
dhcp: T3316: Disable Kea services
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This is a roundup commit to 0be277647 ("T5511: Cleanup of unused directories
(and files) in order to shrink image-size") that dropy empty/commented out
live-build hook scripts.
|
|
|
|
|
|
Daemon configuration is now generated during boot via vyos-1x repo.
See https://github.com/vyos/vyos-1x/pull/2245
|
|
|
|
Add the '/config' directory for live image boot
One of the reasons the DHCP-server uses lease from this directory T2958
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This reverts commit 0b91d71b9cd7e9641287433ea0d0fed3982edb23.
Somehow FRR does not like it to be started with no logging daemon present and
Smoketests fail.
|
|
|
|
auditd logs must no be displayed for journalctl
mask it
|
|
|
|
|
|
Babeld support has been merged https://github.com/vyos/vyos-1x/pull/1800
however I just noticed `/etc/frr/daemons` came from this file.
|
|
debian: T5003: Upgrade base system to Debian 12 "Bookworm"
|
|
|
|
|
|
This reverts commit 8e6d765be123be9d937970ee96b7d6d0b5053ed5.
This breaks existing configurations:
https://forum.vyos.io/t/yesterday-and-todays-build-causes-network-interface-getting-corrupted-vyos-1-4-rolling-202301280924-amd64-iso
|
|
UDEV contains a default rule triggered early-on which renames all
NICs by their index to eX, systemd-udevd subsequently renames the
eX interface to ethX. Systemd-udevd can fail to rename the iface
if it still has resource locks from the prior renaming which then
fails to apply all manner of configurations resulting in a booted
zombie which cannot handle L3 traffic.
Fix the concern by removing 62-temporary-interface-rename.rules
from /etc/udev/rules.d during the cleanup hook executed in
data/live-build-config/hooks/live/82-cleanup-udev-rules.chroot.
Testing:
Boot-tested in OpenStack under identical infrastructure-as-code
states. Verified DHCP-assigned routes, execution of cloud-init,
and configuration stanzas injected through cloud-init applied to
the FW and system.
|
|
|