Print

[BinaryDr0]

A while ago there was a flaw in Windows Vista.  Windows Vista would control permissions according to the executable process name. So say 1.exe is a critical windows process, rename malware.exe 1.exe, and the perms are in place (IMG:style_emoticons/default/wink.gif) . If you still don't understand, rename notepad.exe to winlogon.exe and run it. Once notepad opens up try to kill the process via taskmanager. Moving on...

   Here's my theory.

   If I were to mount the Xbox360 HDD and replace an XBX that's not in use with a custom renamed XBE, should it run?
if I were to write a text file and save it as text.pdf it's still a text file. Xbox360 is backwards compatible making the file-header valid for execution and it's renamed, and used to replace a previous XBX. That way the Xbox360
will not return an error.

   Lets say that the XBE is alot smaller than the XBX. You could SEEK_END and NULL BYTE dummy package the XBE to match the bit size of the XBX to be replaced.

mv  /home/BurningDr0/arbitrary_code.xbe /mnt/sda/default_file_on_drive.xex

360HDD -> /mnt/sda

This post has been edited by BinaryDr0: Sep 9 2007, 09:36 PM

[Sonic-NKT]

the 360 cant execute Xbox1 files! cause its a totally different hardware and system... the 360 emulates the whole xbox1 system for its backward compatibility.

[BinaryDr0]

Anyway to make an XBX via c/cpp? If so you could use the same method just with an XBX from scratch.

[Reaper527]

also, your file will be lacking a digital signature. this will prevent it from being executed.