So in other words, use the dev mode without a license and they'll ban your ass.
Watch this become how the XB1 is cracked.
the devkit code: slightly less useful than the konami code but much easier to remember
Its like a cheat code for your dashboard!
Just speculation but I think if anything substantial could be done through this dev mode it would be a bit more difficult to enable.
So what's the point.
[QUOTE=Socram;43051836]Just speculation but I think if anything substantial could be done through this dev mode it would be a bit more difficult to enable.[/QUOTE]
Yes because Microsoft has only been doing smart things this past few years.
[QUOTE=Zombie man70;43052568]Yes because Microsoft has only been doing smart things this past few years.[/QUOTE]
Microsoft would not leave in the ability to enable something that allowed anything serious to be done. They could quite easily have it enabled by software updates, not a secret code.
I don't think there were any exploits for the Xbox 360's indie dev equivalent.
I'm too lazy to read the article so excuse me if they mention this but these dev-settings are meant for a future update which will allow indie devs to make games for the xbone.
[QUOTE=Jsm;43052625]Microsoft would not leave in the ability to enable something that allowed anything serious to be done. They could quite easily have it enabled by software updates, not a secret code.[/QUOTE]
Tons of people working on same code. Someone adds it to test something and forgets to remove it, it gets overlooked when getting ready for release. Happens all the time with large projects like this. It might not lead to anything, but with the first reaction from Microsoft being "Ohh no, don't do that" it seems it wasn't meant to be left in.
[QUOTE=Sam Za Nemesis;43051403]So probably there's something that could be exploited there, the Xbox One OS (at least should) run over a sandbox, if this can violate this sandbox there should be a way to run unsigned code outside the hypervisor[/QUOTE]
Microsoft aren't stupid enough to let stuff run outside of the hypervisor, on the 360 only the first stage bootloader ran outside it (And all that did was load the encrypted code for booting the console) and even that ended up getting exploited.
Considering they eventually want this to become for norm for developers, they aren't going to leave holes in the security in there.
[QUOTE=TheDecryptor;43053856]Microsoft aren't stupid enough to let stuff run outside of the hypervisor, on the 360 only the first stage bootloader ran outside it (And all that did was load the encrypted code for booting the console) and even that ended up getting exploited.
Considering they eventually want this to become for norm for developers, they aren't going to leave holes in the security in there.[/QUOTE]
Xbox'es sandboxes are like: yo dawg lets put each app in a sandbox in an app sandbox then in a user sandbox for the privileged sandbox to the root sandbox.
[editline]3rd December 2013[/editline]
[QUOTE=cani;43052709]Tons of people working on same code. Someone adds it to test something and forgets to remove it, it gets overlooked when getting ready for release. Happens all the time with large projects like this. It might not lead to anything, but with the first reaction from Microsoft being "Ohh no, don't do that" it seems it wasn't meant to be left in.[/QUOTE]
It is meant to be left in, does nobody remember this? [url]http://www.eurogamer.net/articles/2013-08-20-microsoft-unveils-xbox-one-indie-developer-self-publishing-program[/url]
[editline]3rd December 2013[/editline]
Microsoft, despite what you may think about the company, is actually making it easier to start developing for the Xbox! What a concept!
Yeah, each stage in the 360 bootloader was encrypted, and the previous stage was responsible for verifying and decrypting it.
Then each layer in the running system also had encryption applied, Microsoft sure liked their encryption.
[QUOTE=TheDecryptor;43054070]Yeah, each stage in the 360 bootloader was encrypted, and the previous stage was responsible for verifying and decrypting it.
Then each layer in the running system also had encryption applied, Microsoft sure liked their encryption.[/QUOTE]
I personally love how Microsoft took the blanket approach whereas Sony took a more in depth chain of trust that got cracked anyway. And the PS3 somehow always gets more publicity about being cracked. Even when we have things like Xbox JTAG, the 0800 drive firmware for burning replica xbox dvds for use on custom firmware drives. I personally found cracking and modding the Xbox a funner experience than the deep knowledge PS3 required in some ways.
[editline]3rd December 2013[/editline]
Ok fair enough it was pretty hard to crack, and props to egohot etc.
Sony and Microsoft both went fairly similar routes (Encrypted firmware, decrypted by the previous stage bootloader, etc.), the problem Sony had was a rookie mistake in that their encryption implementation was fundamentally broken (As in, they didn't use random numbers, meaning that their encryption method instead turned into a fairly simple maths problem)
With the 360, you could do a hardware hack to get the first stage bootloader to skip verification checks of the second stage bootloader, allowing the attacker to bypass the hypervisor and gain full access. Same end result, but much harder to exploit and couldn't realistically be expected (or worked around)
Sony got more media attention because it was a text book case of how not to do encryption.
Sorry, you need to Log In to post a reply to this thread.
