Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
Intel and everyone else knows that restricted boot environments for personal computers (desktops and laptops) will be hugely profitable. Entertainment companies love it -- they can deploy a new kind of DRM that won't be defeated for years (see: PS3).
SecureBoot is not a DRM system (for now). If SecureBoot is on, the requirement is that the code executed before ExitBootServices() has to be signed. All code executed after that doesn't. So for example one can create a Boot Loader like EFILinux that will be signed and conform to the specification, and that can load unsigned kernels, and those unsigned kernels can contain any code. The kernel may emulate an EFI interface (like loaders for osx on BIOS), and load Windows kernel, patching it and then starting.
Or, you on PCs that have it turned off, you can create your own EFI application that will load instead of windows's boot loader that will override the GetVariables() functions, so that if the windows kernel queries it, it will return that the SecureBoot is On. It can also patch the kernel itself in memory before starting it.
My main concerns are: Roughly how many users are going to share one public IP? Is this going to break bittorrent, Skype, or other p2p applications? If yes, how could an ISP ever get away with it? Millions of people use these applications every day. There are privacy concerns as well: if someone sharing a public IP with me does something nasty on the internet, could I be dragged into it? Sounds scary. Also, I'm an avid gamer, and many of my online games have servers that ban hackers by IP — I assume I would get banned along with them?
Finally, if all of the above fears prove true, do you think that ISPs are still actually going to roll with massive NAT-ing?"
Shortly before the counternotice for the second takedown notice was posted, GitHub recieved a third DMCA takedown notice from Sony demanding the removal of 1160 Git repositories, most of them forks of fail0verflow's PS3 tools. Most, although not all of them have been removed."
Link to Original Source