O_MAYEXEC — explicitly opening files for execution
O_MAYEXEC — explicitly opening files for execution
Posted May 12, 2020 4:37 UTC (Tue) by Cyberax (✭ supporter ✭, #52523)In reply to: O_MAYEXEC — explicitly opening files for execution by NYKevin
Parent article: O_MAYEXEC — explicitly opening files for execution
Running "curl | bash" is at least honest about its possible impact.
Posted May 12, 2020 5:27 UTC (Tue)
by NYKevin (subscriber, #129325)
[Link] (1 responses)
I don't dispute that. My point was merely that a smart malware author would probably choose a different host, in practice, most of the time. That is a vastly different claim from "PyPI software is always safe," which I certainly did not say. Rather, my claim is more focused on the possible remediation after a malware event. If you know you got it from PyPI, you can pass that information on to security researchers and authorities, who can then study the malware and make recommendations to others. If you got it from curl | bash, who's to say the site is even still there?
Posted May 12, 2020 5:34 UTC (Tue)
by Cyberax (✭ supporter ✭, #52523)
[Link]
Pretty much the only semi-reliable package source are native Linux distribution packages. And even that is likely borderline.
Posted May 12, 2020 9:41 UTC (Tue)
by ballombe (subscriber, #9523)
[Link]
O_MAYEXEC — explicitly opening files for execution
O_MAYEXEC — explicitly opening files for execution
O_MAYEXEC — explicitly opening files for execution
curl | bash provide a correct sense of insecurity while being rather inconvenient. Much less likely to lead to a disaster.