Chase Venters wrote:
Yeah, so to wrap this malware conversation up -- the most effective
way to implant malicious code in Linux is to crack into developer
machines and sneak the changes in.
And hope that someone doesn't notice.
The maintainer will. Over and over, we see maintainers tell developers
to fix their patch - often the problem is something as small as
"bad withespace" or "stupid name for a variable".
Now try to get a backdoor in, and see the maintainer get a fit over
the changes that are clearly unrelated to the problem mentioned
in the changelog.
And if you succeed with the spyware anyway, then someone will notice
the strange packets going out. That you cannot prevent, and it will then
be tracked down. Or you get a backdoor in? It will be found as soon as
it sees some use, or likely earlier with all the more or less automated
vulnerability chacking going on.
Helge Haftinjg
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
