By entering this site you need to consent to the use of cookies and their functional use according to this privacy policy. Cookies help us to provide the functional services of the website. Kindly read the below message of use and consent to the use.
The following cookies are stored and shared when accessing this website:
- Internal cookies for the MediaWiki site. This is used for user authentication and article modifications.
- Third-party cookies from Google providing services for Google AdSense and Google Analytics
We will never use data collected outside of the above scope.
* the second time is using 128-bit AES CBC encryption in the archive data,
* the second time is using 128-bit AES CBC encryption in the archive data,
* and the third time is using 128-bit AES CTR for the WPA2 encryption.
* and the third time is using 128-bit AES CTR for the WPA2 encryption.
+
+
== Remote Distribution and Initiation of System-Updates ==
+
+
As part of the data/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.