this post was submitted on 22 Jul 2024
267 points (95.6% liked)

Technology

59123 readers
2973 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
267
Let's blame the dev who pressed "Deploy" (yieldcode.blog)
submitted 3 months ago by [email protected] to c/[email protected]
68 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 19 points 3 months ago (1 children)

Reminds me of Microsoft's response when one of their employees kept trying to get them to fix the vulnerability that ultimately led to the Solar Winds hack.

https://www.propublica.org/article/microsoft-solarwinds-golden-saml-data-breach-russian-hackers

[–] [email protected] 7 points 3 months ago (1 children)

And the guy now works for CrowdStrike. That's ironic.

[–] [email protected] 3 points 3 months ago (1 children)

I’m imagining him going on to do the same thing there and just going “why am I the John McClain of cybersecurity? How can this happen AGAIN???”

[–] [email protected] 1 points 3 months ago

His next job might look at his job history and suddenly decide that the position is no longer available.