SleeplessCityLights

joined 11 months ago

Using encryption on files systems is fine, but the Microslop Bitlocker implementation is awful. In any ecosystem that is not fully regulated BitLocker is a liability. I have had colleagues that could beat it.

[–] SleeplessCityLights@programming.dev -1 points 3 months ago (2 children)

When I worked at an MSP, BitLocker cost companies thousands of dollars when it did something strange. User error has very catastrophic consequences with BitLocker and nobody that actually cares about security uses BitLocker. From my professional experience it is malware. The places where I have seen it used on purpose was because of policy bullshit and everyone agreed that it was a hindrance rather than an advantage.

If you fully inform them on the situation, they will be cool with it. We are all in this shit together, well until everything falls apart. Add a [] to the prefix on each statement, who the fuck cares. It was the LLM that did it, not you and you were forced to use it.

[–] SleeplessCityLights@programming.dev -1 points 3 months ago (4 children)

BitLocker is basically malware, so who fucking cares. Far more people have it accidentally on and get locked out than people that have purposefully activated it.

[–] SleeplessCityLights@programming.dev 0 points 3 months ago (2 children)

Have it write all of your logging code for you, it may be inaccurate but it is the least damaging place to take the hit as you can just manually search in the source code for where the print was from. They always do something stupid and non uniform making most statements traceable indirectly.

[–] SleeplessCityLights@programming.dev 0 points 3 months ago (4 children)

If your metric is usage, it is incredibly easy to game, just send agents on wild goose chases all day long and never accept the results.

view more: ‹ prev next ›