Ok, I am a bit tired of explaining everything many times over, so here is a summary of all information related to halo 3 modding.
Halo 3 resigning is at the moment, impossible. If there is a resigner, it is not publically available. The halo 3 maps are protected by an RSA/SHA1 hashing scheme. The SHA1 hash is calculated from offset 0x300 to EOF (End of File). This hash is then encrypted with an RSA2048 (256-byte) encryption. This encrypted hash is though to be stored at the offset 36C, and is 256-bytes long.
The main problem in resigning halo 3 maps is the size of the modulus. the modulus is 256-bytes long, or 617 decimal digits long. This makes factoring the modulus quite a problem.
The second alternative is to use a hybrid-360. A hybrid-360 is a standard retail 360 that has been converted to a dev-kit. There are major complications to this as well. The first is that no public tutorial on how to convert a retail unit is available. The second complication is that even if you do manage to find a hybrid 360 (or even a standard Dev-kit), only a selected few actually know how to play modded maps with it.
The reason for this is that the map encryption doesn't lie within a hybrid 360, but within Halo 3 itself (a common confusion). So while a dev-kit might be able to run unsigned code, it can't force halo 3 to bypass it's map check.
Now, many people have found various programs that offer a "Resign" button, and quickly jump to the conclusion that this can be used to make modded maps which will actually work. However in truth, they won't. Just like in halo 2, halo 3 uses yet another signature, CRC (cyclic redundancy check). This signature was used make sure that maps were copied over correctly, and so in truth, halo 3 is the first time that bungie implemented security checks.
So in truth, just wait until a custom boot kernal for the 360 comes out. This will provide 2 things. Firstly, a custom boot kernal could allow Anthony to release his patched halo 3 default.xex game file. This file will bypass the security (that is if he patched it correctly). It will also not allow you on xbox live, so that people can not cheat over xbox live. And last, it would allow modding many more games than just halo 3.
There are also many people who think that they can access their halo 3 DLC, extract it from the LIVE files, mod them, and inject them back in. There are many flaws in this. The major flaw is that the halo 3 map files will still need to be resigned with the RSA/SHA1 hashing scheme, so they are on the same page as modding the original maps. The second problem is that there is no public tool that can be used to mod CON/LIVE/PIRS files. So you would have to bypass 2 encryptions to mod DLC maps.
A few programs that are used for halo 3:
- Engineer 1.1 - Generally used for basic tag editing.
- Johnson 1.4 - Mainly used for research, also includes scripting functions.
- Mango 1.0 - Also generally used for research.
The sources for all of these programs as well as binaries can be found at halomods.
And for those of you who just don't wanna read all of this, i'll just summarize it for ya.
Quote: Originally Posted by me
You can't mod maps atm...
clear?
Halo 3 modding explained
Halo 3 modding explained 
Not removing this until Steve pays me.
Linear Mode
