120

A case study in why credentials are revoked before firings.

you are viewing a single comment's thread
view the rest of the comments
[-] jqubed@lemmy.world 32 points 2 weeks ago

I remember working at a TV station where I got caught in a round of layoffs. Most of us they told in advance, that our last day would be in six weeks, but they laid off an engineer at a smaller station and had him gone immediately. They also deleted his account that day, and that’s when they discovered he was running a lot of station processes through his own account. I think it took the corporate engineers a week to get everything back to a fully operational state.

[-] oeuf@slrpnk.net 8 points 2 weeks ago* (last edited 2 weeks ago)

I do something like this at my workplace. I guess it gives me leverage, but the main reason is that my boss drags his heels so much when I try to improve the workflow that it's easier for me to just crack on without his knowledge.

Apparently this is common enough that there is a term for it.

[-] jqubed@lemmy.world 4 points 1 week ago

I think the latter was the main reason. It sounded like his boss really had no idea what was going on or how to make things work. It was only the two of them at that station and they laid off the guy who was actually doing everything.

[-] femtek@lemmy.blahaj.zone 2 points 1 week ago

Yeah, so many git credentials are tied to the account that created them.

this post was submitted on 12 May 2026
120 points (100.0% liked)

Pulse of Truth

2405 readers
186 users here now

Cyber Security news and links to cyber security stories that could make you go hmmm. The content is exactly as it is consumed through RSS feeds and wont be edited (except for the occasional encoding errors).

This community is automagically fed by an instance of Dittybopper.

founded 2 years ago
MODERATORS