News for hackers. Stuff that matters.
Re:Detecting the use of “curl – bash” server side (2016) by jbj on Wednesday December 09, 2020 @05:31AM (#25357210)
Maybe it is because the website owner has full authority to change anything at their discression, while git packages usually exists in an ecosystem that can be observed and tracked.
Re:Detecting the use of “curl – bash” server side (2016) by londons_explore on Wednesday December 09, 2020 @05:54AM (#25357347)
git allows rewriting history. It doesn't seem unlikley one could come up with an attack which gives a malicious git clone to one user, and then rewrites history so all other users later don't see the maliciousness.
Re:Detecting the use of “curl – bash” server side (2016) by filmor on Wednesday December 09, 2020 @06:25AM (#25357518)
Rewriting history has absolutely nothing to do with this. In a VCS that doesn't allow this, I could just hand out repo1 and repo1+malicious-patch. In both cases (as with git as well), I can detect this by comparing hashes.