News for hackers. Stuff that matters.

A comment on GitHub Notification Emails Hijacked to Send Malware. Parent comment

Re:GitHub Notification Emails Hijacked to Send Malware by godelski on Friday September 20, 2024 @06:35AM (#41600562) 

  > Do people really fall for scam like that?
I routinely get people opening issues on my projects asking where the source code is or how to fine tune their models on different data or even how to install pytorch.... There's a lot of people on GitHub that don't know the first thing about coding. There's a lot of people on GitHub that don't know how to use Google... This even includes people with PhDs...
[ Parent | on HN ]
Re:GitHub Notification Emails Hijacked to Send Malware by NeveHanter on Friday September 20, 2024 @06:41AM (#41600603)
I've also seen an issue on GitHub asking project author to add an entry in README.md with instructions on how to clone the repository...
[ Parent | on HN ]
Re:GitHub Notification Emails Hijacked to Send Malware by tom_ on Friday September 20, 2024 @07:38AM (#41600980)
Actually worth doing if the repo uses submodules.
[ Parent | on HN ]
Re:GitHub Notification Emails Hijacked to Send Malware by godelski on Friday September 20, 2024 @01:39PM (#41604075)
https://lmgtfy.click/?q=How%20do%20I%20clone%20a%20repositor...
[ Parent | on HN ]
Re:GitHub Notification Emails Hijacked to Send Malware by keybored on Friday September 20, 2024 @02:58PM (#41604656)
The naive way in this case wouldn’t be to make an issue: How do I clone this repo? I see it has submodules

The naive way would be to just clone the repo without any (apparently) options.

I can attest to this because that’s probably what I would do.

The readme would not resolve a problem that someone knowingly had. It would resolve an unknown upcoming problem.

[ Parent | on HN ]
Re:GitHub Notification Emails Hijacked to Send Malware by tom_ on Friday September 20, 2024 @08:44PM (#41606642)
Yeah, git clone --recursive is the main thing I suggest. But unlike Google I include the exact command that you can copy and paste into the terminal to clone the specific repo in question.

And if you're reading the README after cloning it already, there are instructions for sorting that out too, also suitable for copy and paste.

Or if you downloadeded the ZIP from GitHub - I'm sorry. But you won't be left too confused, at least you won't if you read my README, because my README covers this situation as well.

(Also: don't forget to git submodule update after changing branch! But if you're noting everything my README tells you, you won't.)

[ Parent | on HN ]