QUOTE(InterestedHacker @ Dec 24 2005, 12:04 PM)
It's FACT that the media checks happen more than once! Due to the way in which the security works, you would likely need the original disk (for that game) to boot from every time, so that kinda makes the whole thing pointless! Sorry for being sharp, just fed up of reading the same posts over and over.
It rotates like this:-
1) Why can't we use a buffer over flow.
2) Why can't we hot swap the discs.
3) Why can't we FTP. (This one REALLY winds me up no end)
4) Why can't someone hack MCE so I can watch DivX movies.
It's good to suggest things, but this has been suggested before, and before, and before.
I agree with you on several points. I'm tired of answering most of the questions. But I'm also tired of seeing ideas shot down or misunderstood.
"Hey, can we use the save game from..." No. But I don't think that necessarily means the end of buffer overflows. Just as the securiteam article I linked to detailed, even with hardware support and special attention to buffer overflow exploits, they couldn't thwart it in x86. There's a chance for the exploitation opportunities to exist in the 360 yet. MS left the door open for this one though. They do have a "safe C library", which replaced strcpy and family with safer versions of it. No; I'm not talking about strncpy; they have a strcpy function which they claim to be safer. However, chances are they didn't include it in the 360 toolchain. In a document once linked on the Xbox scene homepage about how developers without a dev kit could get ready for writing code for the 360, they had a note about only using strcpy in cases where they *absolutely* needed the performance (because with 3 cores at 3.2 GHz, you're hurting for those vital picoseconds. ;-) ). This precaution seems to allude to the fact that MS may be aware that though they've tried, buffer overflow just may be a method of exploitation we may be able to leverage. Though the old ways of doing it are probably rendered useless...we'll have to do something other than a save game. The problem with the question though, is that the people asking it only know of a "buffer overflow" from reading the Xbox 1 "How does the game save hack work?" document. Most have no clue the mechanics behind such a hack. Fewer have actually ever written one. Still fewer can manage to write one for a program which they do not have the source for.
When I say hotswap; I'm not talking about a PS2 style hotswap. I don't expect to be able to insert PD0 and a backup Condemned, and be able to play the backup. I do, however, think that there may be a method of exploitation through *a* hotswap. But I'm going to shut up until I get my 360 and can poke at it myself.
And yeah; the FTP and MCE questions are just retarded. If we could get our code on the Xbox to open the FTP server, we wouldn't have any of the other problems in running our own code. ;-) And Xbox 360 may be incredible; but MS is still working on the whole "making little endian, x86, 32 bit codecs work on a big endian, PPC, 64 bit architecture." ;-). I like it. That's sig.