Post #2491079
2026-05-13 07:37 UTC
Replies (2)
-
@derpeter@chaos.social 2026-05-13 07:52
@mcfly@milliways.social Choose your explanation: a) Oh sorry we used Copilot to develop this and it might went rough. b) That's a left over from a debugging feature we are terrible sorry c) That's a feature not a bug, please keep walking
-
@Rairii@labyrinth.zone 2026-05-13 08:05
@mcfly@milliways.social not really, i've found enough vulns to dump bitlocker keys before. to me, it looks like just someone fucked up basically modern NT has a system called "Velocity", where code can be gated on one of "always on, default on, default off, always off", when it's set to always off it's effectively ifdef'd out of the build, and the settings can be different per branch. Basically the idea is when a coder develops a feature they have it set to always off except in their branches, and later on it's set to one of the other three (default on/default off can be used for A/B testing), I assume this functionality was supposed to be set to always off except for a couple of branches, and someone set it to always on by mistake when merging something else.