Submission + - Slashdot is dead 3
An anonymous reader writes: I saw it with my own eyes
Submission + - How to fix Slashdot Beta? 17
Forbo writes: Since the migration to Slashdot Beta was announced, it seems all meaningful discussion has been completely disrupted with calls to boycott and protest. Rather than pull an Occupy, what can be done to focus and organize the action? What is the end goal: To revert entirely to the previous site, or to address the problems with the new site?
Comment Re:Does not work on Windows Phone (Score 1) 123
I don't think it works on anything but webkit. I've tried in in opera mobile for android, and in mobile firefox.
Comment Re:Servers and Laptops (Score 2) 296
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.
Comment Re:What's the most an ATOM Net-Top can take? (Score 1) 543
Atom CPUs have 64bit and PAE, but are limited to 4GB. The computer I'm using right now is Atom D525/NM10/ION2 with 4GB RAM.
Submission + - IPv6 Transition: Carrier-Grade NAT
caius112 writes: I've tried searching for information about the precise drawbacks of massive carrier-grade NAT-ing, which may be to come in the following months. Nothing close to exhausting comes up, so I guess it's time to Ask Slashdot.
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?
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?
Submission + - GitHub Sends DMCA Counternotice to Sony (github.com)
Plombo writes: After receiving a second DMCA takedown notice from Sony demanding the takedown of another repository related to PS3 homebrew, GitHub sent a counternotice. In addition to the standard legalese about how the repository doesn't infringe on Sony's copyrights, it notes that "Sony is attempting to abuse the DMCA to avoid public embarrassment (too late) and put the genie back in the bottle (too late), and has failed to meet the minimum requirements for giving DMCA notice (no details provided on which source code lines infringe copyright). the exposure of sloppy crypto implementation on Sony's part in no way infringes on copyright or makes available any of their proprietary internal software".
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.
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.
