Technology

59680 readers

3264 users here now

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

Our Rules

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

Approved Bots

founded 1 year ago

MODERATORS

214

New York Times warns freelancers of GitHub repo data breach (www.bleepingcomputer.com)

submitted 5 months ago by AnActOfCreation@programming.dev to c/technology@lemmy.world

34 comments fedilink hide all child comments

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

[–] CaptainBasculin@lemmy.ml 50 points 5 months ago (17 children)

GitHub sucks with private repositories anyways. If any company needs a sizable source control utility, just hosting their own GitLab instance will be way cheaper and safer than entrusting it to Microsoft and paying an unnecessary enterprise rate to GitHub.

[–] Dark_Arc@social.packetloss.gg 41 points 5 months ago (6 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.

load more comments (1 replies)

load more comments (4 replies)

load more comments (14 replies)