The NXE and CON Resigning.

[ManBearPig06]

Quote: Originally Posted by halodu2de

i could have people save it through my fileshare quickly or just custom games but yea maybe ill do different packages so like monthly or weekly or certain number and get one free

I would suggest not doing it through a fileshare if you don't want to get your account and fileshare banned on halo.

[Halodu2de]

if you do it quickly i dont think they can ban you (like for 10 seconds)

[gabe_k]

The amount of time doesn't matter. Bungie most likely keeps a record of all files uploaded.

[Halodu2de]

thats what i was wondering

[quic]

well, ****. im not going through all the dog **** to get my kv, so just **** it. i guess we can look at the bright side of things, enjoy the update, play the game, and at least waist less time modding and more time appreciating the beauty of xbox. maybe there will be a ray of hope when recon comes out

[scooter204]

Quote: Originally Posted by halodu2de

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?

halodu2de do you have a working resigner (i still hav one)

[Luxurious Meat]

Quote: Originally Posted by Haxalot88

I've checked several combonations in the system update so far. I checked them in any XEX's that might have them, along with some accompanied binary files. Nothing stores SHA1 hashes (of the entire public key, or any portion there-of) or any parts of the keys from what I have so far checked. I'll check a few more things though.

The revoked keypairs are stored in a LIVE or PIRS signed file on the NAND flash.

[ddxcb]

LoL guess wat my con resignner is 360GS

Quote: Originally Posted by ddxcb

LoL guess wat my con resignner is 360GS

To bad 360gs uses an web based resigner that you have to be a member to use.

[nickcas]

Quote: Originally Posted by Luxurious Meat

The revoked keypairs are stored in a LIVE or PIRS signed file on the NAND flash.

If you had an exploitable console could you just remove the entire container that holds the blacklisted keypairs? Or does even removing a container completely break the sig?

[legendary xH2x]

Ok i dont understand what you guys are really talking about but does anyone have a new resigner (not banned) that they can give out?<_

Quote: Originally Posted by legendary xH2x

Ok i dont understand what you guys are really talking about but does anyone have a new resigner (not banned) that they can give out?<_

Then read what scar posted...

[Haxalot88]

Quote: Originally Posted by nickcas

If you had an exploitable console could you just remove the entire container that holds the blacklisted keypairs? Or does even removing a container completely break the sig?

It will probably at-the-least expect to find that container there. So you couldn't completely remove it, and cannot modify it yourself. Best bet would to pull the container from the previous release (pre-NXE) and use that as a replacement. Unsure of what hashes are involved in the NAND though.

[Luxurious Meat]

Quote: Originally Posted by Haxalot88

It will probably at-the-least expect to find that container there. So you couldn't completely remove it, and cannot modify it yourself. Best bet would to pull the container from the previous release (pre-NXE) and use that as a replacement. Unsure of what hashes are involved in the NAND though.

If you were ona vulnerable kernel you could try to remove the file, but as soon as you upgrade to go on XBL your just gonna get it again.

[Supermodder911]

Quote: Originally Posted by Haxalot88

It will probably at-the-least expect to find that container there. So you couldn't completely remove it, and cannot modify it yourself. Best bet would to pull the container from the previous release (pre-NXE) and use that as a replacement. Unsure of what hashes are involved in the NAND though.

Well usually when files are missing from the NAND, the 360 errors(E60, E61, etc, etc), so yea.

Anyway, heres some info regarding the revoked keys.

Kernel functions, "XeKeysRevokeUpdateDynamic" and "XeKeysRevokeSaveSettings" are used to update and save the revoked keys. A little reversing shows the file is at "\\Device\\Flash\\crl.bin" on the consoles flash. So if anyone is really interested, feel free to start reversing, I have other things to do.

[GaryGodX]

Quote: Originally Posted by unknown v2

If someone from Microsoft gets their hands on a file signed by that KV, they will probably ban it.

That wouldn't make to much seance because when you download a map from custom games or bungie.net doesn't just change the KV to your own then anyone who downloaded any modded map will be ban then and we all know that won't happen!!!

[DJ Shepherd]

Quote: Originally Posted by GaryGodX

That wouldn't make to much seance because when you download a map from custom games or bungie.net doesn't just change the KV to your own then anyone who downloaded any modded map will be ban then and we all know that won't happen!!!

thats because bungie doesnt have the actual container file, the kernel extracts the file out of the container, bungie gets the container, then when you download just the file, the xbox kernel stores it in the container file with your keyvault

[loogash]

Quote: Originally Posted by unknown v2

If someone from Microsoft gets their hands on a file signed by that KV, they will probably ban it.

so if i signed a modded halo 3 map with my KV and they found that modded map and madded the KV would that meen that all my saves, gamertag, noramly made maps and things would stop working?

also would my KV change after it gets banned or will it keep resiging saves with the KV and getting the corrupt sign up as its been banned?

[unknown v2]

Quote: Originally Posted by loogash

so if i signed a modded halo 3 map with my KV and they found that modded map and madded the KV would that meen that all my saves, gamertag, noramly made maps and things would stop working?

also would my KV change after it gets banned or will it keep resiging saves with the KV and getting the corrupt sign up as its been banned?

If the KV that gets banned is the one your 360 uses and you update your box so that it's listed as banned, all your saves will be corrupted, even things that aren't modded, because it's like your 360 is using a signer with a banned KV.

Your KV doesn't change by itself.

[Shadow LAG]

Let me put it to you guys this way. All stolen/public resigners are now dysfunctional, In my opinion Microsoft did hard working modders a great service. So heres how this works, any and all resigners being made public will be banned, Creating a new one will not help. If you get your own keyvault congratz you deserve your resigner, if you cannot or refuse to learn or think its too much trouble, you shouldn't have had a resigner in the first place. Now you can always use a invite-only resigner that Microsoft cannot get their hands on, and I think this is a quite efficient approach seeing as the people being accepted in usually are done so selectively and very few people being selected in are prone to abuse con, because well lets face it. Nobody wants an xbox that can't run any content. So really your two choices are as stated before.

1 - Actually work hard and do something for yourself and get your keyvault.
2 - Get into a selective private society by proving yourself worthy and not abusive.

This is really how con resigning should have been like from the start.