[citation][nom]rhino13[/nom]As jsloan just mentioned, there are two things to note about this. First, They were running Windows 7 on a virtual machine. Meaning that they could be running files prior to the initial loader. If you are running Windows 7 on the hardware this is impossible.Second, this is not just a Windows 7 problem. By rewriting the right segment of code even Linux/Unix machines will become incapable of realizing the hack.But again this is impossible if you are running Linux/Unix directly on the hardware as well. I must assume that the editors at Tom's are smart enough to know this and are just printing this trash to generate conversation. But, still, shame on you Tom's what is the point of such fear mongering.If we have learned something here today it is that you should not allow someone to boot from a portable drive on your machine and then load your OS into their VM.[/citation]
i realized that they were hacking a vm, i was just saying you can't stop people form hacking an os, because they can always go to the level before the os and hack that. for example if i can get control of the boot process, whether off computer or vm i can control hack the os being booted, if i can get access to the hardware where the os is stored, whether on a harddisk, thumb drive, cd, ect, i can always hack it. it does not matter if encrypted or not, encryption makes it a little harder, but not impossible. bioses can be hacked and the boot process is not magical, it can be easily hacked so the hacker sets themselv in ring 0 before the os load and can even run the os in a vm. why not, it would just take a hacker a bit of effort to mod a vm that acts like a gateway to the hardware and keeps the os thinking that its running normally. also, if you can patch the cpu microcode you can hack that.
what i also wanted to say is that it's not microsoft os alone that is at risk, it's any software or anything that will run on the cpu.
i've written code that boots up before the os does, that wraps bios calls, and then fakes a boot of the os, the os calls the wrapped bios calls being non the wiser. a hacker could do the same. it's not that hard to change the partion table, the partition booter, the os boot record or boot code, ect. and now with flash bios its not that hard to change the code on those either. in the old days you had to physically remove the bios and external hardware to read and write the bios roms, but not no more, the code to flash bios you can get over the internet, and some bios have it built in, so you just have to make bios calls...