- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Nov 21 2024
Nov 20 2024
Nov 19 2024
Nov 17 2024
Nov 13 2024
Nov 11 2024
Nov 10 2024
Nov 8 2024
Nov 7 2024
Nov 2 2024
Nov 1 2024
Thanks for the contribution.
Oct 24 2024
Oct 14 2024
There was a licensing issue with tailscale - you would need a container to solve this or use headscale instead.
Oct 13 2024
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.
Oct 12 2024
Yes, that‘s correct behavior.
That's actually an interesting idea to force config commit messages if archive option is set to git
@SteveP you need to install the MOK, see https://docs.vyos.io/en/latest/installation/secure-boot.html
For those keen to test secure boot support please see https://docs.vyos.io/en/latest/installation/secure-boot.html
The above gives that it will be somewhat tricky to add your own module afterwards unless you do a full recompile since the key used to sign the kernel lives in the /tmp and is lost once the ISO have been created.
Oct 10 2024
Oct 7 2024
If the device is not even listing in lspci it's more of a Hyper-V thing then VyOS.
Oct 6 2024
Oct 5 2024
Sep 30 2024
Sep 29 2024
I can not immediately recreate the issue:
Sep 28 2024
We should have two variants - Kernel build in and OFED driver