this post was submitted on 16 Jun 2024
214 points (98.2% liked)

Technology

59569 readers
3825 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
 
  • The New York Times suffered a breach of its GitHub repositories in January 2024, leading to the theft and leak of sensitive personal information of freelancers.
  • Attackers accessed the repos using exposed credentials, but the breach did not impact the newspaper's internal systems or operations.
  • The stolen data, amounting to 273GB, was leaked on 4chan and included various personal details of contributors as well as information related to assignments and source code, including the viral Wordle game.
you are viewing a single comment's thread
view the rest of the comments
[–] Dark_Arc@social.packetloss.gg 41 points 5 months ago (2 children)

Hot take: GitLab is sluggish, buggy, crap. It is the "Mega Blocks" of source control management.

If you have source files that are more than a few hundred lines and you try to load them on the web interface, forget about it.

They can't even implement 2FA in such a way that it isn't a huge pain to interact with. There's been an open issue for over 7 years now to implement 2FA like it is everywhere else, where you can be signed in to more than one device at a time if you have 2FA enabled (https://gitlab.com/gitlab-org/gitlab/-/issues/16656).

Not to mention this was not a GitHub failure, this was a failure by the NYTimes to secure their developer's credentials. This "just in house/self host everything and magically get security" mentality that's so prevalent on Lemmy is also just wrong. Self hosting is not a security thing, especially when you're as large of a target as NYTimes. That one little misconfiguration in your self hosted GitLab instance ... the critical patch that's still sitting in your queue ... that might be the difference between a breach like this and protecting your data.

[–] barsquid@lemmy.world 9 points 5 months ago (2 children)

I will never use GitLab after seeing CVE-2023-7028. It should simply not have been possible with any reasonable security posture. I do not want their software running on my machines.

[–] JackbyDev@programming.dev 3 points 5 months ago

Jesus Christ... That's a doozy.

[–] Dark_Arc@social.packetloss.gg 2 points 5 months ago

Yikes, thanks for sharing that one!

[–] crazyminner@lemmy.ml 8 points 5 months ago (2 children)
[–] PlexSheep@infosec.pub 3 points 5 months ago

I self host Forgejo for a pretty long time now. I put my personal stuff there and if something seems like the public might like it I mirror it to GitHub and Codeberg. Forgejo is amazing and will be even more amazing when federation support gets stable.

[–] Dark_Arc@social.packetloss.gg 1 points 5 months ago

Haven't used it first hand, but I think it's more promising.