GitHub | https://github.com/chux0r |
Bluesky | https://bsky.app/profile/chux0r.bsky.social |
Xwitter | No://abandoned.dont.go.there |
GitHub | https://github.com/chux0r |
Bluesky | https://bsky.app/profile/chux0r.bsky.social |
Xwitter | No://abandoned.dont.go.there |
I've not touched my source for so long, I might need to take a hot second to recall what I was doin, and what might have possessed me to write things the way I did. My comments should help.
Shit who tf wrote these comments.
Breach comms amirite? Turn the same old sleight-of-hand in hopes to downplay things and color your impression of the event. What the hell. Here's a cheat sheet for ya:
"To our knowledge..." -> We have plausible deniability here and are clinging to it for dear life to avoid the accountability that comes with having knowing about facts beforehand and bungling things utterly. In fact, at this very moment we may or may not be in an isolation chamber with our fingers in our ears, screaming LALALALA.
"The information was not accessed..." -> The threat actor definitely established enough permission to grab everything. But we don't seem to have logs of them doin' anything. See also: "To our knowledge..."
"The information was not exfiltrated..." -> We found that stuff on a different net, queued up on external storage hanging off some IT worker's workstation. Also, no logs, but very normal stuff, we assure. Also, also, see "To our knowledge".
"No account numbers or log-in credentials were compromised..." -> Please, please baby Jesus, do not remind them to ask us what information was actually compromised.
"The information was compromised..." -> Who saved those access logs? Fire that guy.