 |
|
| r.a.d.menu is empty. Please, specify correct XML data file in the ContentFile property, populate the menu at run-time or define menu structure inline. |
D:\WebRoot\MCMS\KeycorpCms_V2\Site\KC
|
|
|
|
|
|
|
|
| r.a.d.menu is empty. Please, specify correct XML data file in the ContentFile property, populate the menu at run-time or define menu structure inline. |
D:\WebRoot\MCMS\KeycorpCms_V2\Site\KC
|
|
|
|
What is the AMD (additional MULTOS data)?
|
| |
|
The AMD is information that is supplied by the implementor to the MULTOS CA to create enablement certificates. The structure of such data is specific to the implementation. Most implementors will include the ability to add new primitives or codelets in the AMD. These primitives or codelets will be loaded into EEPROM during enablement. As primitives are native-code, it is essential that AMDs for a given implementation be controlled by the implementor of a MULTOS. This is because any change to native code could threaten the ITSEC E6 security of the implementation. AMDs are created by the MULTOS implementor and sent to the MULTOS CA. If a card issuer wishes to include any codelets into the EEPROM of MULTOS cards via the AMD, the codelet image needs to be sent to the implementor (contact MULTOS support) who will format this information into the required format and forward as a complete AMD to the MULTOS CA.
|
| |
|
|
|