Rumor: PartnerNet Bricking Kits?

I agree with Tyler, has to be some kind of common link.

Hawk

 

I never said anything about passing keys around anywhere. I mentioned that MS could insert portions of code signed with the private boot loader key on a XEX file if they wanted to make anything to run on more authority than the OS level. (Mechanisms for such would need to exist on the hypervisor though. If someone can step up and *prove* that such mechanisms do not exist, then this theory is fubar.)

The hypervisor would then check these "special" pieces of code with the public bootloader key and if it passes, get loaded and appended to the existing hypervisor code.

That's just as secure as the CB is right now. I don't see any kind of room for security breach on this scheme as it would be then protected by the normal XEX signing first, and then the payload would be then protected by the second (boot loader) key pair.

And then if nobody ever dumped the CPU MASK ROM we would not even know the public boot loader key. (what pirates call the "1BL key")

 

You can't make a claim, then ask people to disprove it, you're supposed to prove it yourself...

Also, the 1BL key isn't an RSA public key. If you're talking about the RSA public key in the 1BL, it still doesn't make sense because there's no code that shows that key being used to verify XEX signatures.

 

can't get to the cache folder, jtag sees dev hdd as unformatted and xplorer360 does not recognise either

any apps out there that read dev HDDs?

 

Okay my post oddly just disappeared so I'll say this again.

You will either need to hook it up to a dev or Jtag and FTP. Dev HDD's are formatted differently.

 

I won't prove it because I'm not an software specialist.

I also won't bite on flamebaits.

It was a theory, nothing else.

Sometimes the tone of these "challenges" may make them appear hostile and then it's where flamewars start. I have no interest on that.

Thank you.

 

yeah read my post again

 

Have you attempted an FTP? I believe a dev is the only thing that can get the contents off but wouldn't hurt to try.

 

yes ftp does not see anything

 

Then seems like Dev is your only solution at the moment. Can you get an image from your HDD? I can mount it on my dev and take a look.

 

ALL --- I JUST DELETED A BUNCH OF POSTS --- ALL

Talking about the bricks = ON TOPIC

Insulting other users, raising shit, commenting that other people are off topic, commenting on the quality (or lack thereof) of the thread = DELETE BAIT

They've all been removed.

-hl718

 

I also cannot find anything to open my dev HDD. Nothing recognizes it and I've tried a lot of programs.

 

Just use linux to make an image of it.

You should be able to find/trace out what you need, even with a simple hex editor.

That is assuming that, the xdk nuking doesn't wipe the hdd too. :S

 

So nobody has torn apart the contents of their drive yet, CSI-style?

 

Why don't you guys just disconnect your routers from the internet, and leave everything plugged in to the network then browse through Neighborhood? Although, your kit was hit, right bear?

 

By the way I am not sure about it but I believe that it may be possible for Microsoft to shadow boot a kernel/hv straight from the network and use it to blow efuses. This is devkits we are talking about after all.

 

i really wish I could do that :thumbsup:

unfortunatly all i have is a blank screen and 3 flashing red lights lol

 

Tut on that stickied. No need to unplug anything.

 

There were a few major leaks that tweaked out Microsoft.

There was the attempted Splatterhouse sale. As mentioned earlier, that didn't go over well.

There was also your Forza 2 leak lllsondowlll. Making a dev build of a current gen, first party title publically available as soon as the JTAG hack came out...well let's just say it was a big slap in the face and a major "Fuck You" to Microsoft.

XBLA leaks are relatively low level compared to full version games in terms of how high up the food chain they go.

The obvious point of action here are the illegit or "phantom" kits. Nuke everything that is already supposed to be destroyed and you eliminate a big part of your problem. After are we're talking about hardware that shouldn't currently exist.

If none of these kits are in the wild, then the incentive to track down dev software is greatly diminished. Who wants to pay or trade for a disc they can't properly run?

Payload over a network connection is simple when you control the box.

The hypervisor *is* the core OS running on the machine. Everything else is essentially running in a VM. He who controls the hypervisor controls the hardware.

On a dev kit you can run custom apps, but you still only have the hardware access that is allowed by the hypervisor. The hypervisor can shut down *ANYTHING* it deems unfit.

This is why the JTAG hack is technically impressive. It bypasses all of the security in the hypervisor. Not an easy task.

Put simply, if you have a dev kit and you hook it up to Microsoft's network, Microsoft (as the only ones that control the hypervisor) can do pretty much anything they want to do with it. Anything.

If you want a good overview on how a hypervisor works, read up on the Hyper-V whitepapers published by Microsoft. While a PC isn't an Xbox, a basic comparison would be running in a VM that someone has setup for you. You may have full control over the OS in the VM, but no matter what you run (Windows, Linux, OS X, etc.) no command you run in the VM is going to "break out" and let you take control of the actual machine.

Why is this "...going a bit too far" for Microsoft?

Every kit that is getting bricked is Microsoft's property. If you own something, you can do what you want with it, including destroy it.