Line 95: |
Line 95: |
| Can you send me also, please? --[[User:Jocopoco|Jocopoco]] 19:33, 27 November 2011 (CET) | | Can you send me also, please? --[[User:Jocopoco|Jocopoco]] 19:33, 27 November 2011 (CET) |
| :::Just because Nintendo SDKs can build software for retail doesn't mean they include the retail AES key(s). When devs send binaries for RSA signing Nintendo takes care of encrypting the binaries with the retail keys as well.(AFAIK they have *never* included retail keys in their SDKs) --[[User:Yellows8|Yellows8]] 03:31, 28 November 2011 (CET) | | :::Just because Nintendo SDKs can build software for retail doesn't mean they include the retail AES key(s). When devs send binaries for RSA signing Nintendo takes care of encrypting the binaries with the retail keys as well.(AFAIK they have *never* included retail keys in their SDKs) --[[User:Yellows8|Yellows8]] 03:31, 28 November 2011 (CET) |
| + | :::: ^ This is true but DSi/Twl development builds actually do run on retail systems. ;P --[[User:Jl12|Jl12]] |
| + | :::: Also, I think you mean "release" builds. Development builds have debugging functions enabled and aren't optimized. The SDK can build retail (release) builds that include optimization and are stripped of debugging information and some internal debug flags. This is to get ready for retail ROM mastering. It doesn't mean it uses retail encryption or signing methods. (It doesn't.) --[[User:Jl12|Jl12]] |
| | | |
| I wouldn't think they contained retail keys, Yellow8, just it contained some keys (probably dummy keys) called Common Header Keys and they seemed interesting for a moment imho I didn't see your post there lol I'm still considering whether or not they're legal. In a way, they are legal because I'm not technically hired by Nintendo so the CXIs, CIAs, etc I make are not copyrighted by them like retail or licensed developers, but in another way it's not legal because I am using part of the lib to make the files. Gah!--[[User:Xcution|Xcution]] | | I wouldn't think they contained retail keys, Yellow8, just it contained some keys (probably dummy keys) called Common Header Keys and they seemed interesting for a moment imho I didn't see your post there lol I'm still considering whether or not they're legal. In a way, they are legal because I'm not technically hired by Nintendo so the CXIs, CIAs, etc I make are not copyrighted by them like retail or licensed developers, but in another way it's not legal because I am using part of the lib to make the files. Gah!--[[User:Xcution|Xcution]] |
Line 100: |
Line 102: |
| | | |
| Ok, after some thought and looking around here I shouldn't have a problem posting non-commercial (and not copyrighted for developers, ie DevMen or Config) CIAs because user Jl12 has done this without having a problem with copyrights. CFA is essentially a bundle of CIAs so I shouldn't have a copyright issue there as long as the CIAs inside are not commercial and not developer copyrighted (ie I can't post commercial or DevMen/Config/etc), however according to Jl12's upload of his custom CIA it is OK to upload custom CIAs, and in essence CFAs. I'm looking into the legality of other formats, though.--[[User:Xcution|Xcution]] | | Ok, after some thought and looking around here I shouldn't have a problem posting non-commercial (and not copyrighted for developers, ie DevMen or Config) CIAs because user Jl12 has done this without having a problem with copyrights. CFA is essentially a bundle of CIAs so I shouldn't have a copyright issue there as long as the CIAs inside are not commercial and not developer copyrighted (ie I can't post commercial or DevMen/Config/etc), however according to Jl12's upload of his custom CIA it is OK to upload custom CIAs, and in essence CFAs. I'm looking into the legality of other formats, though.--[[User:Xcution|Xcution]] |
| + | |
| + | * Please only post what you've written/compiled yourself, no files from the SDK(s) or that has been mastered by N. ( such as roms, etc. ). --[[User:Jl12|Jl12]] |
| | | |
| Today I'll start documenting a little bit of what I find. Currently I'm still learning so this'll probably be amended a lot. | | Today I'll start documenting a little bit of what I find. Currently I'm still learning so this'll probably be amended a lot. |
Line 120: |
Line 124: |
| | | |
| Hi Elisherer, is not exact format as [[CCI]] actually. Just I show the most plain objects. CSU does '''not''' have SDK informations shown (example : [SDK+NINTENDO:CTR_SDK-0_14_23_200_none]) like CCI has, or CSU has not this in plain text like CCI has.. --[[User:Xcution|Xcution]] | | Hi Elisherer, is not exact format as [[CCI]] actually. Just I show the most plain objects. CSU does '''not''' have SDK informations shown (example : [SDK+NINTENDO:CTR_SDK-0_14_23_200_none]) like CCI has, or CSU has not this in plain text like CCI has.. --[[User:Xcution|Xcution]] |
| + | |
| + | * Note, you can't decrypt .CSU with the same development keys a CCI/CIA can be decrypted with, not sure if that's because it has a different set of keys or because of a difference of format though. I admit I haven't dug deeply. CCI/CSU do appear very similar and both need to be burned to a blank cartridge to be ran. --[[User:Jl12|Jl12]] |
| | | |
| '''CTR Fun Facts :''' | | '''CTR Fun Facts :''' |
| | | |
| Before release, CTR was in development back in 2009 under the codename "Horizon". Unfortunately lib doesn't give what "CTR" stands for =p--[[User:Xcution|Xcution]] | | Before release, CTR was in development back in 2009 under the codename "Horizon". Unfortunately lib doesn't give what "CTR" stands for =p--[[User:Xcution|Xcution]] |
| + | |
| + | * Sup Xcution. this is gshock, though you probably could guess that from the userid. \o/ |
| + | * Maybe you guys can consider taking this conversation to n-dev.net lol --[[User:Jl12|Jl12]] |