[woodruffw]

GitHub's response time on malicious repositories is often lackluster. However, from conversations with folks at GitHub, my suspicion is that this is because they're being starved for resources, not incompetency or maliciousness.

This (IMO) points to a perverse reality: things need to get worse before they can get better. In other words, Microsoft probably needs to feel more pain (in the form of negative revenue pressure) before they take their own platform responsibilities (vis a vis not distributing malware) seriously.

We say this play out recently with improvements to GitHub Actions security, I expect we'll see the same here.

(Edit: to be absolutely clear, I have first-hand experience that GitHub's security folks work extremely hard, and are often doing the kinds of invisible, thankless "deck-swabbing" work that nobody even thinks about. They're just under-resourced.)

[reddozen]

> in the form of negative revenue pressure

Is this happening? GitHub status page is a Christmas tree for 3 quarters and comically had an incident 10 minutes after the "we're working hard on fixing stability!" blog post published.

The free market has responded by buying GitHub Enterprise to avoid the incidents. So we've effectively rewarded GitHub's lack of serious engineering with more money. Doesn't seem like they have any real pressure to improve.

[woodruffw]

It's happening for Actions security, at least. I don't know about their other services.

[VenturingVole]

Whilst I personally don't have first hand experience with GitHub's security team - your experiences and suppositions perfectly match my own general observations with our sector.

I've had the pleasure of working with absolutely outstanding security professionals, doing exactly what you see - relatively thankless work.

Due to the alignment of incentives, it can in fact be worse than merely thankless and face internal opposition - so the perverse reality of Microsoft/GitHub needing to feel more pain is sadly likely true.

This article's author is wonderfully honest about having not worked at a larger company and is right to call out the issues that are all about organisational alignment/ownership.. or lack thereof.

You could never pay me enough money to be responsible for security at GitHub though, that's for sure.

[Fr0styMatt88]

Reminds me of when Windows security problems hit critical mass in the early-2000s and Microsoft went all-in on addressing it (this started in the XP days IIRC).

[creshal]

The post-release XP service packs, to be precise. XP's release was a perfect storm of events: Suddenly, millions of home users receiced an OS that had dozens of networked RPC services running in the background, and received DSL modems around the same time that exposed their computer directly to the internet. A slightly suboptimal combination at a time when software firewalls were a separate product you had to buy for a hundred dollars a year, if you even knew they were a thing.

[UqWBcuFx6NV4r]

See also: Steve Gibson advocating for doing away with raw sockets and the nerds of that era losing their minds over such a supposedly preposterous call.