<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-build.git/data/certificates, branch rolling</title>
<subtitle>VyOS image build scripts (mirror of https://github.com/vyos/vyos-build.git)
</subtitle>
<id>https://git.amelek.net/vyos/vyos-build.git/atom?h=rolling</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-build.git/atom?h=rolling'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-build.git/'/>
<updated>2026-04-28T14:27:36+00:00</updated>
<entry>
<title>Kernel: T861: add custom VyOS CA to Kernel builds for later module signing</title>
<updated>2026-04-28T14:27:36+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2026-04-28T14:25:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-build.git/commit/?id=a29a2dfa0fa34743508664ca3d0564a923f904d5'/>
<id>urn:sha1:a29a2dfa0fa34743508664ca3d0564a923f904d5</id>
<content type='text'>
With this addition we can always sign a Kernel module later and ship it if
needed, without re-compiling the Kernel.

Kernel will report:
[    1.223891] Loaded X.509 cert 'VyOS Networks Secure Boot Signer 2025 - linux: 6ca57e2add335babd08da69b48c70693edd2b037'

Issuer: CN = VyOS Networks Secure Boot CA
        Validity
            Not Before: Apr 26 09:07:06 2025 GMT
            Not After : Apr 24 09:07:06 2035 GMT
        Subject: CN = VyOS Networks Secure Boot Signer 2025 - linux
</content>
</entry>
<entry>
<title>T861: use secure-boot certificates from data/certificates</title>
<updated>2025-03-18T15:19:39+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2025-03-16T19:10:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-build.git/commit/?id=a02b10b2ba4197c4dcd84eef053e4ab94995295b'/>
<id>urn:sha1:a02b10b2ba4197c4dcd84eef053e4ab94995295b</id>
<content type='text'>
</content>
</entry>
</feed>
