Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

So you’re going to continue to host images that have severe remote code execution exploits?

With no way for the person who posted them to ask people not to use them?



It appears that even after nonapology they still don't get the fucking problem.

The whole thing only needs docker infrastructure getting hacked because it used some of the now-orphaned containers to complete the shitshiw


I wonder what a court would think about who'd be legally liable there?

BigCo or GovDepartment gets popped via a known exploit against a fixed bug in an OSS project, but GitHub has prohibited the project from updating the explicable image they host without paying a ransom of $420/year?


> So you’re going to continue to host images that have severe remote code execution exploits?

That seems an great way to take some very significant reputation hits.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: