Egregoros

Signal feed

*sigh*Ber nard

@brnrd@bsd.network

(Free)BSD, security, Libre-/OpenSSL, tinkering by night.
Bored-out Security Architect by day.
Running, swimming, cycling, hiking when I have the time and energy.

Posts

Latest notes

@dch

If you can create something that parses https://www.oracle.com/security-alerts/cpuapr2026.html, filters all MySQL Server and Client related vulns and populates the vuxml entry, that'd be something the port maintainer (@joneum) could use.

What I really meant is something to replace the vuxml process. Wasn't there something going on in the project about this exact issue?

I would be looking for something that pulls the info from an external resource, allows the port maintainer to filter out entries that don't apply on FreeBSD, and push it to something that's easy to query. The whole blockquote part in vuxml is duplication of effort, unnecessary in my view, unless the vuln is FreeBSD specific and not available in an external registry.
CVE? -> Look up in CVE databases
GHSA? -> Look up in Github
...?

@dch @joneum and myself have a tough job maintaining the MySQL and MariaDB ports. There are multiple versions to maintain, they're big, have loads of options and dependencies, take long to build, ...
Having a cumbersome vuln registration process just isn't helping. The vuln registration must happen prior to updating (actually committing) the port so you have the vulnid from vuxml.