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.
this post was submitted on 16 Jun 2024
0 points (NaN% liked)
Technology
59373 readers
8326 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
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.
Forgejo?
Haven't used it first hand, but I think it's more promising.
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.
Yikes, thanks for sharing that one!
LOL same thing happened to Google. When will these people learn MS does not care about your data?
I don't see what Microsoft has to do with this. The article says the repos were accessed with stolen creds.
As The Times told BleepingComputer last week, the attackers used exposed credentials to hack into the newspaper's GitHub repos.
I don't know what "exposed credentials" are but if they were accessed with "stolen" creds there would be no "hacking", just logging in.
So... Unless Microsoft directly leaked those credentials, I don't see how it would be their responsibility.
...because they didn't adequately protect them?
It is not Microsoft's job to protect your password, it is yours.
Or did you assume it was GitHub itself that was compromised? The article doesn't say where the creds were obtained. My guess is plain old phishing. Though it could also be cred-stealing malware, that seems to be making a comeback, in the form of browser extensions and mobile apps. Either way, those aren't Microsoft's fault.
Or did you assume it was GitHub itself that was compromised?
That's the way it reads to me.
My guess is plain old phishing.
Going back to my previous comment, if it was obtained through fishing, there would be no need for "hacking".
“Hacking” is a catch all term for security breaches, including phishing to the general public.
No it is not
Yes it is. You can be a pedantic a-hole all you want, but “hacking” includes phishing, social engineering and pretty much any other form of access control circumvention to the general public.
Edit:
Also from the article itself
A 'readme' file in the archive states that the threat actor used an exposed GitHub token to access the company's repositories and steal the data.
Exposed GitHub token is very likely someone messed up and either exposed a token or was victim to an attack that could pull the token. Those are not uncommon and have happened to a lot of companies.
This is "hack" like the kid that guessed your grandma's Facebook password is "ilovecats1953", "hacked" Facebook.