module.sig_enforce [KNL] When CONFIG_MODULE_SIG is set, this means that modules without (valid) signatures will fail to load. **Note that if CONFIG_MODULE_SIG_FORCE is set, that is always true, so this option does nothing.**
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Mon, Oct 14
will you add podman exporter as well?
Sun, Oct 13
It seems the bug even if configuration applied in one commit:
set interfaces ethernet eth1 vif 21 set interfaces ethernet eth1 vif 22 set interfaces bridge br1 member interface eth1.21 isolated set interfaces bridge br1 member interface eth1.22 isolated
Does this also mean that we can no longer use unsigned drivers with non EFI systems? I can't at the moment. It would be nice if we could choose to use the pre 6.6.52 behaviour if we want to.
I have also signed my Realtek driver with the same cert but that did not work. Perhaps we could pick that back up over on T6713
The rolling images are currently not yet secure boot signed. We are in the design and validation how we can to this from a CI/CD perspective in a secure way.
I have installed the latest rolling release and upon reboot I am getting:
Sat, Oct 12
That's actually an interesting idea to force config commit messages if archive option is set to git
Hi c-po
For those keen to test secure boot support please see https://docs.vyos.io/en/latest/installation/secure-boot.html