...damn... I'm a bit tired of this discussion...
Andre, are you trying to say that you don't need to have r00t to make
some hdd-barbecue? If so wouldn't Linus have applied the patch? It's
obvious that you can make silly things mixing some holes and d-destroyer.c
Your patch is helpful, but it's "security through obscurity", you can
still fry hdd after getting r00t, only diffirence will be a bigger exploit
and more time wasted on writing it... you are exaggerating or you can't
clearly explain what do you mean... but patch should go in anyway...
BTW: software may (but don't have to) damage BIOSes, firmwares, CPUs
(programming PLL on mobo), older monitors, ISA/PCI cards (programming
southbridge to get ISA/11Mhz and PCI/41.5Mhz)... etc...
just imagine advanced worm (similar to the one discribed in some
lcamtuf's project) making use of all hardware "features"... ugh...
The ONE and ONLY solution is r00t without direct access to hardware...
cheers
-- Bartlomiej Zolnierkiewicz <bkz@linux-ide.org>
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/