On 8 Aug 2023, at 11:04, Marta Rybczynska <[email protected]> wrote: > Instead of manually looking up new CVEs and determining what point > releases the fixes are incorporated into, add a script to generate the > CVE_STATUS data automatically. > > First, note that this is very much an interim solution until the > cve-check class fetches data from www.linuxkernelcves.com directly. > > > This is coming Ross, this is coming... > > But I have a question. We do prefer to have a solution that runs completely > on the > build machine, without automatic rebuilds from the YP? I'm asking because for > the > solution I'm working on we're adding a pretty big git repo to each build > (~130MB).
That’s a pretty sizeable fetch but not astronomical. That’s the linux_kernel_cves repository, right? At least with git it’s a one-time hit for the initial fetch and then just the deltas on updates. Ross
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#185734): https://lists.openembedded.org/g/openembedded-core/message/185734 Mute This Topic: https://lists.openembedded.org/mt/100603502/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
