Andrew Lilley Brinker

Andrew Lilley Brinker

@alilleybrinker.com

Supply chain guy writes to public ledger. Developer Security @ Anthropic Opinions are my own

2.9K followers590 following8.8K posts

You know his opposition has nothing when the scandal is “sometimes he plays basketball at the police academy”

Chris Sommerfeldt@c-sommerfeldt.bsky.social

New: Mayor Zohran Mamdani and a group of his friends have been secretly using the NYPD Police Academy’s gymnasium in Queens to play pickup basketball — scrambling some operations at the facility. w/ @grahamrayman.bsky.social & Joe Anuta www.politico.com/news/2026/10...

This has more details on the mechanics of the failed vote and the next steps for C++26 to still possibly ship, though shipping might require dropping contracts to secure the required NB votes.

train-it.euThe result of the C++26 DIS ballot | Train ITThe national bodies didn't approve the C++26 draft in its DIS ballot, and the No votes point to contracts. The numbers, why every vote in a national committee counts, what the committee can do next, a...
Andrew Lilley Brinker@alilleybrinker.com

IMO, if C++ really fails to ship contracts here, thereby slipping them to C++29 at the earliest, it’s another nail in the coffin and C++ will continue on its slow decline toward being a legacy language.

The premise of the game is players play multiple rounds racing around a relatively simple board. Each racer character has a single power, and each power can be explained in 1-2 sentences. Yet the intersection of powers can lead to absolutely chaotic turns.

It also makes modeling and ranking racer value difficult, because often racers‘ value is relative to what other racers are on the board. In fact, the strategy lies in racer recruitment up front, then racer selection each round.

View full thread

Previously, the best you could do was check against the official JSON schema, but that didn’t cover all the checks that the REST API actually does. This library fixes that. It’s JSON schema validation plus all the other checks, and it’s used inside the API itself so the library won’t drift.

There’s more to do for improving the experience of working with CVE Records (IMO defining clear versioning rules should be a top priority), but this is a valuable step to make life easier for the roughly 550 CNAs enrolled in the program.

This solves a problem for CNAs. They want to know their records will be accepted by CVE Services’ REST API, with a clear separation between internal drafting (where private/sensitive info might slip in) and publication after internal approval.

In addition to the abject racism, the rest of the new rules make clear r/opensource is committed to being a highly insular, exclusionary community. Projects posted must be successful long-term projects with active communities. The person posting must be a long-time active Redditor.

hikikomorphism@hikikomorphism.bsky.social

hooooo boy we don't like this no we don't > If you don't speak English, you need to find a different community. We cannot distinguish between AI-written and AI-translated. Since you don't speak English, you can't even verify yourself if it translated correctly. www.reddit.com/r/opensource...

They appear committed to being a racist, insular club for their existing participants, which is the absolute antithesis of the welcoming, inclusionary culture I know and love in OSS.

Good news in vuln management world: CNAs of Last Resort issue less than 5% of all vulnerabilities now. That’s a win for the quality of CVE records. No org is equipped to do high-context vuln-report assessments from security researchers across *all* software or hardware.

Andrew Lilley Brinker@alilleybrinker.com

Got curious and had Claude whip these up from the cvelistv5 repo.

There’s a weird ecosystem of vuln management greybeards who spend a lot of time fixated on the quality of CNA-LR CVE records, while missing how the importance of those has been dropping. The CVE program recognized 10 years ago that they needed federation to scale, so they made it happen.

We’re in a similar situation today with vulnerability “enrichment,” with NVD and independent downstreams unable to keep up. CVE’s adopted a federated strategy with Authorized Data Publishers and by moving more expectations onto CNAs directly. IMO this is right and I hope they expand ADP enrollment.

You might wonder why the graph started ticking up around ~2016. That’s when CVE began aggressively enrolling more CVE Numbering Authorities! CVE is a federated system, and CNAs are the orgs approved to issue new CVE Records. In Jan 2016 there were 23 CNAs. Today there are 559.

Andrew Lilley Brinker@alilleybrinker.com

Spending years on an assurance feature you fail to ship, when you have 3 year release cycles, and *this* is happening?

View full thread
Andrew Lilley Brinker@alilleybrinker.com

Good news in vuln management world: CNAs of Last Resort issue less than 5% of all vulnerabilities now. That’s a win for the quality of CVE records. No org is equipped to do high-context vuln-report assessments from security researchers across *all* software or hardware.

You might wonder why the graph started ticking up around ~2016. That’s when CVE began aggressively enrolling more CVE Numbering Authorities! CVE is a federated system, and CNAs are the orgs approved to issue new CVE Records. In Jan 2016 there were 23 CNAs. Today there are 559.

Andrew Lilley Brinker@alilleybrinker.com

Spending years on an assurance feature you fail to ship, when you have 3 year release cycles, and *this* is happening?

This federation avoids bottlenecking CVE issuance on a small number of orgs. It also means CVEs can be issued by orgs with more domain expertise in the specific software/hardware affected by the vuln! (disclosure: I previously worked at MITRE on the CVE program, though not in MITRE’s CNA side)

Coordinated disclosure is good, especially since a description of a vuln is often enough for AI to discover it even if you don’t publish a PoC exploit. You don’t *have* to coordinate, but I and others will think less of you when you prioritize self-promotion over protecting users.

The handling of these Tailscale vulns, from posting about them online (a partial disclosure), to the branded name and website, to the refusal to engage in coordination, all benefit attackers while scaring defenders without equipping them to act. It’s juvenile.

IMO, if C++ really fails to ship contracts here, thereby slipping them to C++29 at the earliest, it’s another nail in the coffin and C++ will continue on its slow decline toward being a legacy language.

Spending years on an assurance feature you fail to ship, when you have 3 year release cycles, and *this* is happening?

Andrew Lilley Brinker@alilleybrinker.com

IMO, if C++ really fails to ship contracts here, thereby slipping them to C++29 at the earliest, it’s another nail in the coffin and C++ will continue on its slow decline toward being a legacy language.

Regarding vulns decaying exponentially: AI pushes the reasonable limit you can climb that asymptote closer and closer to 0 by driving cost per discovery downward.

Andrew Lilley Brinker@alilleybrinker.com

1. Formal methods exist and are becoming much easier / cheaper with AI. We can prove strong properties up to the limit of the formal system. 2. Vulnerabilities decay exponentially (see link), and we can get asymptotically assured about the security of individual software.

Please use SSVC to help decide what action to take if you’re managing vulnerabilities. Check your CVE records for CISA ADP’s enrichment with SSVC data!

cisa.govStakeholder-Specific Vulnerability Categorization (SSVC) | CISA
Andrew Lilley Brinker@alilleybrinker.com

The shoreline of “easily exploitable” keeps rising. We don’t have the benefit of measurable ”bits of security” like we do for tuning cryptography strength, so we shouldn’t consider exploit ease in risk rating or action-taking IMO.

Lobsters admins trying to fix the mess of how LLMs are treated on the site is laudable, but likely to be very painful since the site has grown an extraordinarily hostile and abusive culture generally and toward LLMs specifically.

CA has been dealing with early versions of this and politicians and voters have mostly responded by putting their heads in the sand.

David Roberts@volts.wtf

A memo from senior insurance-industry officials warning that insurance modelers are being pressured to downplay climate in their models & that many insurers are already planning their exist from key markets. An explosive fuckup on the scale of the mortgage crisis is building.

Cosmically funny when a long time mystery has a totally benign answer

Filippo Valsorda@filippo.abyssdomain.expert

Anthropic found the origin of the NIST elliptic curve seeds: they were generated with drand48()! No one was seriously worried, but this should put some FUD to rest, completing the NIST ECC rehabilitation arc… just in time to be retired in favor of PQ. Also, we raised $36 Ki for ISRG. Yay!

Disappointed the Dodgers lost, but wow the Brewers put on a show. Well deserved win, and I hope they take the whole thing. I’m also glad this punches huge holes in MLB’s arguments for a salary cap. Players should be paid what they’re worth!

I’m not trying to maximize productivity or anything, and feel no pull that I *need* to work on projects when I can. It’s just fun to have the option! Relatedly, I might have new stuff to share soon!

For the Pending New Thing, before making it public I‘ve had Claude flag every piece of Claude-written prose (docs, code comments, website copy) for me to review. The goal is that no written material for humans passes to release without me either replacing it by hand or iterating closely with Claude.