fs_objects.html
3.19 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
<html>
<head>
<title>Objects Stored on Module Flash</title>
</head>
<body>
<h1>
<p align="center">
Objects Stored on Module Flash
</p>
</h1>
This following list indicates the major categories of data that
must be stored on Module Flash (external). A short description
for each entry is included here and links to documents with
more detailed information are provided. For some objects there
are "C" headers checked in, but the location of these headers
is not included at this time.
<ul>
<li> <b>eTickets for personalized content:</b> these are stored in a
single file. TBD, any optimizations to pull pieces out that are
not strictly required for launch (primarily content metadata).
(<a href="../security/Structures.htm">details</a>).
<li> <b>Secure Kernel:</b> 64K at beginning of flash
(<a href="first_app_load.html">details</a>).
<li> <b>boot-app eTicket:</b> 2 copies to ping-pong via sequence number
(<a href="first_app_load.html">details</a>).
<li> <b>boot-app:</b> linked via list with starting link in eTicket
(<a href="first_app_load.html">details</a>).
<li> <b>Content Re-encryption Key List:</b> contents managed by SK,
storage managed by system app, to which it appears opaque (will
add link to updated system app doc).
<li> <b>Game state info:</b>
<ul>
<li> <i>Per-game data -</i> mimicks eeprom and flash on cartridge.
One file per game on module, safety box file for games not
presently on module (but for which an eTicket is owned and
possibly played).
<li> <i>Controller Pak(s) -</i> these span multiple games. One or
more could be present.
</ul>
<li> <b>Content meta-data:</b> used by system app to assist content
(game) browsing. Exact location is tbd, but likely to be in either
content eTicket, first 4K of content, or separate file.
<li> <b>License server certificates:</b> one per license server. Possibly
combined into a single file with a ping-ponged backup
(<a href="../security/Structures.htm">details</a>).
<li> <b>License servers certificate chain:</b> CA chain so above certs
can be verified to root. Possibly combined with above certs in the
same file.
<li> <b>BBID and/or BB certificate:</b> tbd, but at least the BBID must
reside on the module. Possibly, the BBID will be wrapped in a BB
certificate, signed by appropriate server.
<li> <b>BB cert CA chain:</b> certs for tracing signer of bb cert to root.
<li> <b>CRL for eTicket servers:</b> only one required that is most recent.
<li> <b>CRL for CAs:</b> only one required that is most recent. Maybe
combined in same file as eTicket server CRL.
<li> <b>Games:</b> must be layed out on flash to satisfy ATB constraints.
<li> <b>"New" Content:</b> non n64-style compatible content that does not
require ATB layout restrictions or associated game state. This may
also include non-personalized applications loaded by the system app
for supporting functionality such as viewing photos.
<li> <b>File System Metadata:</b> for maintaining file system (will add
link to updated FS description document).
</ul>
</body>
</html>