| Line 1: |
Line 1: |
| | + | 译自[[Download_Play]] |
| | + | |
| | 3DS dlplay有两个dlplay模式：3DS和DS。DS dlplay是只是普通的dsmode dlplay，使用了和从前同的接口和协议。 与DS游戏卡相同，进入dsmode dlplay应用时按住start +select，3DS会禁用拉伸屏幕。 | | 3DS dlplay有两个dlplay模式：3DS和DS。DS dlplay是只是普通的dsmode dlplay，使用了和从前同的接口和协议。 与DS游戏卡相同，进入dsmode dlplay应用时按住start +select，3DS会禁用拉伸屏幕。 |
| | | | |
| Line 20: |
Line 22: |
| | 080: 25 f2 56 c4 19 88 64 13 78 68 e2 | | 080: 25 f2 56 c4 19 88 64 13 78 68 e2 |
| | | | |
| − | == WPA2 加密 == | + | == WPA2密钥 == |
| − | Download Play 协议和所以的本地无线通讯使用相同的WPA2加密机制。输入数据使用 [[Process_Services|EncryptDecryptAes]] 和 [[PSPXI:EncryptDecryptAes|keytype1]] 是一个 0x10-byte 哈希值. Download Play输入的口令是固定的，区别在于每一个本地无线协议。 CTR是一个0x10-byte 经过哈希的16-byte结构，包含了主机MAC地址, 正常应用的titleID中的uniqueID。(然而用于Download Play的uniqueID是固定的)。输出的十六进制加密数据是最终WPA2密码。这个有可能是MD5的0x10-byte哈希值是未知的。
| + | 用于引导单卡联机的可执行通信有一个单独的WPA2密钥，它是由 [[NWM_Services|NWM]] 模块生成的一个随机的十六进制字符串。 |
| − | 引导Download Play可执行文件的wpa2通讯使用上述方法生成的随机十六进制字符串作为密码。
| |
| | | | |
| − | == Broadcasted application data == | + | == 广播应用数据 == |
| − | The Download Play protocol broadcasts 3DS application data in the [[CIA]] format, which contains a certificate chain, a ticket, a TMD, and the actual application itself, in [[CXI|CXI format]]. The broadcasted archive data is temporarily stored as a file on the internal NAND Flash storage, and is kept there until new archive data from a different game is received through the Download Play protocol.
| + | Download Play协议以[[CIA]] 格式广播3DS应用数据, 包含certificate chain, ticket, TMD各一,以及[[CXI|CXI format]]格式封装的应用本体。广播的归档数据临时存储在内部的NAND Flash直至其他游戏通过Download Play协议占用此空间。 |
| | | | |
| − | The CXI application content is again encrypted, this time using 128-bit AES CBC. The encryption uses the decrypted titlekey of the ticket, and the titleid padded with zeros as the IV. To get the decrypted titlekey, the titlekey stored in the ticket must be decrypted using 128-bit AES-CBC with the 3DS common key, and the same IV as mentioned previously.
| + | CXI 应用数据使用了128-bit AES CBC加密. ticket中有加密的titlekey , 和titleID补零构成的IV。为了得到解密的titlekey,ticket中存储的titlekey必须使用128位AES-CBC的3DS公钥解密，以及前面提到的IV。 |
| | | | |
| − | So in actuality, the 3DS application code, as it is being transmitted wirelessly has been encrypted 3 times:
| + | 所以，事实上通过无线传输的3DS的应用程序，经过了3次加密： |
| − | * The first time is using 128-bit AES CTR encryption for the ExeFS of the CXI format, | + | * 第一次使用128位AES CTR加密的CXI格式的ExeFS |
| − | * the second time is using 128-bit AES CBC encryption in the archive data, | + | * 第二次使用128位AES CBC加密的归档数据 |
| − | * and the third time is using 128-bit AES CTR for the WPA2 encryption. | + | * 第三次使用128位AES的WPA2加密CTR。 |
| | | | |
| − | == Remote Distribution of System-Updates == | + | == 远程分布式系统更新 == |
| | | | |
| − | As part of the child distribution process, a 3DS acting as the server in a local Download Play session, can send firmware updates to another 3DS unit acting as the client, through first sending the system update package then instructing the client to install reboot and reinstantiate a connection (which it caches information about temporarily) remotely, if it finds system updates are necessary before distributing the child-application. ( eg. multiplayer game or a demo. ) Like "update" partitions on CTR Cards, this is not an "automatic feature" and not implemented for all Download Play titles.
| + | 作为分布式系统的一部分，一台3DS扮演了本地Download Play服务器的角色，可以给作为客户端的机器发送固件更新。首先发送系统升级包，然后给客户端发送指令安装升级包并重启。 在比如远程连接时 (缓存临时信息)，如果在发现运行分布式子应用(比如多人游戏)必须进行系统更新，就像升级CTR卡的分区一样, 这不是一个“自动功能”，并没有在所有的Download Play titles中实现。 |