by pcmonk on 8/3/22, 5:16 AM with 76 comments
by oefrha on 8/3/22, 7:27 AM
> The attacker creates FAKE orgs/repos and pushes clones of LEGIT projects to github.
Yeah, anyone can push anything to their own GitHub accounts/orgs, including malware. We know that.
Save yourself some time. Flagged.
by raggi on 8/3/22, 6:18 AM
by soruly on 8/3/22, 6:21 AM
and 13K of the search results come from this org
by abctree on 8/3/22, 7:50 AM
Fanatics who believe otherwise will still clone those projects so that they are on sacred ground, but the practice should be frowned upon and fought against.
Another detrimental effect of GitHub is that they have trained users to accept public "forks" (a misnomer) as the usual way to contribute even trivial patches. This lowers the bar for accepting and trusting non-official repositories.
GitHub has devalued the brand of large projects and has introduced the age of industrialized software development by creating an addictive environment where software politicians thrive by manipulating their social networks and working on their personal brand.
by drekipus on 8/3/22, 5:50 AM
Seems like the solution is "don't just copy random github urls into your code" ?
by mcraiha on 8/3/22, 5:38 AM
by rollulus on 8/3/22, 7:35 AM
by jwilk on 8/3/22, 6:10 AM
Huh? What does that mean?
by muppetman on 8/3/22, 5:40 AM
by 3np on 8/3/22, 6:20 AM
by dustinmoris on 8/3/22, 8:01 AM
by thih9 on 8/3/22, 7:55 AM
Source: https://mobile.twitter.com/stephenlacy/status/15547180866572...
by bonzini on 8/3/22, 6:10 AM
by robertwt7 on 8/3/22, 7:01 AM
so this will send data to the hacker's network if we clone and build the wrong repo right?
by rvz on 8/3/22, 5:50 AM
If lots of software released today haven't been pinning their versions on release (especially Electron apps) or signing their commits if they are open-source, then this is a chaotic supply chain attack waiting to happen and is more worse than I thought.
But really it is yet, another reason to avoid GitHub entirely and just self-host using GitLab or Gitea.