![]() | ||
The NXE and CON Resigning.
| ||
![]() |
| | LinkBack | Thread Tools | Display Modes |
| | #1 |
| Retired Staff ![]() | The NXE and CON Resigning. I have seen way too many threads on this so i though i would make ONE informative post. MS has banned all public keypairs (KV.bin) so files resigned with them WILL show up as corrupt, they have NOT done anything else to prevent CON resigning. The fix: Get your own private keyvault and dont give it to anyone. Or: have 2 xboxes, have one updated with the NXE and another without as an offline box. load your resigned file on the offline 360 and re-save it in game. doing this puts your own keypair on the save, making it not be corrupt in the NXE. A keypair is a series of numbers (keys) used to calculate a signature. each 360 has a unique set of numbers. So all MS has to do is ban the public ones to make all files resigned with them show up as corrupt. To get your keypair you need either a launch console that has never been connected to LIVE with a dash version 4548 or lower. OR an Infectus 2 modchip to downgrade to that dash version. either way, it is not easy,So I will not go into more detail on how to do this here. If i see any more threads on this they will be locked. people seem to think that the whole xbox gets corrupted or that all mods are corrupted false, only ones that have been signed by the public key pairs, if you change something like a name or resave it or download it or whatever, it REsigns it with YOUR (unbanned) key pair so that in return makes them work if you resign something with the banned key pair, that and only that save will be corrupted, not your whole xbox unless a save is signed with a banned key pair Last edited by Scar; 11-16-2008 at 04:33 PM. |
| |
| The Following 7 Users Say Thank You to Scar For This Useful Post: | Anonymous Joey (12-02-2008), FtK Shadow (11-17-2008), GTORacer (11-23-2008), halomaster369 (11-22-2008), Tin Can (02-02-2009), Zack3008 (11-22-2008) |
| | #2 |
| Guest | Re: The NXE and CON Resigning. Thank God. So many people asking the same damn question... |
| | #3 |
| Member | Re: The NXE and CON Resigning. Sad, yet true. I don't do much CON modding so I don't care too much. |
| |
| | #4 |
| Team Horizon ![]() | Re: The NXE and CON Resigning. This may seem like a stupid question, but I'd like to know before I spend $100 on an infectus. I have a launch console, and I have NXE. I can still downgrade, correct? None of the updates can stop that? |
| |
| | #5 |
| BANNED | Re: The NXE and CON Resigning. How are we exactly going to get a private key vault? Explain that 'cause I am confused! |
| |
| | #6 |
| Member | Re: The NXE and CON Resigning. |
| |
| | #7 |
| Modding Beast ![]() | Re: The NXE and CON Resigning. if i have a private KV and i want to mod with NXE is it possible for M$ to ban the keyvault if i use it online or if i resign with it and give the mods to someone else and they play it online? |
| |
| | #8 |
| BANNED | Re: The NXE and CON Resigning. not only is the infectus a b*tch to install but you need an old xbox that hasnt hit live |
| |
| | #9 |
| Member | Re: The NXE and CON Resigning. I thought that as long as you have BK 1888 you can timing attack it? Considering alot of the people who deal with it say you cant use it on later hardware revisions, it should work on a launch console. I know it still works with the current dash, Ive talked to a guy who writes the current dash when he wants to play new games and writes the exploitable one when he wants to deal with unsigned code. |
| |
| | #10 |
| Member | Re: The NXE and CON Resigning. Its swapping them that supposedly is the dodgy part. Its repetitive and annoying, and this eases the process. Plus its easy installation, so it seems like a win. EDIT: Nvm what I said. Mistakened this tab for the recent 360 ModChip. Last edited by Holy Ownage; 11-16-2008 at 07:01 PM. |
| |
| | #11 |
| BANNED | Re: The NXE and CON Resigning. well im not to sure entirely on this subject so id go with eazy lulz <3 |
| |
| | #12 |
| 7S Addict | Re: The NXE and CON Resigning. If someone from Microsoft gets their hands on a file signed by that KV, they will probably ban it. |
| |
| | #13 |
| I ****ing dare you ![]() | Re: The NXE and CON Resigning. @ EazyB: yes, as long as BK is at v.1888 the timing attack is still possible (did a few searches). All hardware revisions after the Xenon are patched against the timing attack if i remember correctly. @ Halo2dude: they can ban it easily. If they got their hands on the file, then they could just ban it that way, OR if they have enough reason to, they can simply get the key that is used on whatever modded file you have from the 360 itself. |
| |
| | #14 |
| Modding Beast ![]() | Re: The NXE and CON Resigning. do they have the ability to ban it or is it just a good chance they do? |
| |
| | #15 |
| 7S Addict | Re: The NXE and CON Resigning. |
| |
| | #16 |
| Modding Beast ![]() | Re: The NXE and CON Resigning. is it automatic? And has it been proved they do? |
| |
| | #17 |
| Junior Member | Re: The NXE and CON Resigning. from what that i herd dont blow the E-Fuse or u cant extract the info to make the kv. |
| |
| | #18 |
| 7S Addict | Re: The NXE and CON Resigning. |
| |
| | #19 |
| I ****ing dare you ![]() | Re: The NXE and CON Resigning. With the newest version, they can now update your console at will silently. AKA if they have more keyvaults to ban, next time you connect to live, it'll just download that updated list. |
| |
| | #20 |
| 7S Enthusiast | Re: The NXE and CON Resigning. This really stinks. No seriously, there's something fishy about this...I just can't put a name on it, but something is definitely fishy. And, can someone provide a link to Xbox Scene? Last edited by Sonja; 11-16-2008 at 08:52 PM. |
| |