null
US
Sign In
Sign Up for Free
Sign Up
We have detected that Javascript is not enabled in your browser. The dynamic nature of our site means that Javascript must be enabled to function properly. Please read our
terms and conditions
for more information.
Next up
Copy and Edit
You need to log in to complete this action!
Register for Free
2636014
Multi-Application Smart cards
Description
Mind Map on Multi-Application Smart cards, created by MattSmith129 on 01/05/2015.
Mind Map by
MattSmith129
, updated more than 1 year ago
More
Less
Created by
MattSmith129
over 9 years ago
37
0
0
Resource summary
Multi-Application Smart cards
Memory
RAM
128b -3kb
EEPROM
4b-64kb
1000x slower than RAM to write to
App Data & OS extensions
ROM
3kb - 128kb
Smallest physical space required
Standards
ISO7816
Part 1 - Physical Characteristics
Part 2 - Dimonetions
Part 3 - Electronic Signals / Transmission
Part 4 -Commands for interchage
Application Protocol Data Units (APDUs)
Smart Card APDU Handler
before multi application
Various smart card operating systems (SCOS)
Gemplus
MCOS
MPCOS
OSCAR
programmed lots of different langs
apps had to be installed in advance
designed for specific sprocessors
functions embedded in the SCOS
Monolithic
close coupling of apps and OS
seperation of OS and Applications
EEPROM
Applications
Rom
OS
platforms
MULTOS
SCOS
I/O
Cyrpto
File Management
App Load/Delete
write standard lang
C Code
Java
VB
OUTPUT: MEL compiler
Optimizer/Linker
Off card loader
Certification of Apps
Global Platform
Developed by VISA
Runtime Environment (RTE)
Virtual Machine (VM)
Developer API
SCOS
Card Manager
Federating access control to the card
Registery
card state
command dispatching
instalation/removing apps
security manaagement
managing security domains
asign some privileges to apps
crypto for apps
PIN management
Event Logging
card issuer responsibilities
Load Card Manager keys
set policies for card life cycle
authorize load files
Security Domains
Issuer Security Domain
Rep issuer
Supplementary Security Domains
Rep Apps
Controlling Authority Security Domain
applying policy
Javacard
Java Card API
objects
byte and short types
boolean
single d arrays
Portability
security architecture
Applet sandbox
no pointer use
subset of java language
subset JVM
subset API
API V.10
1996
12kb, 4kb EEPROM, 512b ram
uni-dimensional arrays
operators
boolean
bytes and short types
API V2
1997
introduced crypto
Portability and interop was a issue
class file conversion was vendor specific
4 main packages
javacard.framework
javacardx.framework
ISO7816-4 compatible file system
javacardx.crypto
API V2.1
1999
new applet firewall and restrictive
Interoperable/re sueable
better error handling (exception hierarchy)
supported
packages
virtual methords
objectives
arrays
unsupported
no intergers
no char or string
no dynamic class loading
no garbage collection
Remote Method Invocation (RMI)
Client Application proxied to reader driver
no need for APDU
lifetimes
java card starts at ROM burn in
JCVM Forever
applets start when installed and registered in the registry table
JCVM
Enforces Security Policy
has gone up to EAL5+
PP already set
java code -> std compiler - > class file (byte code) -> coverter tool -> java card byte code - > off card installer
on card installer - > JCVM
dyanamic (apps installed after card issue)
windows for smart card
SCOS
.NET Cards
Sits on top of SCOS
sits on top of OS
liencing costs
java card has significant costs
smart cards types
Contact smart card
contactless smart card
All Communication Through APDU messages
Show full summary
Hide full summary
Want to create your own
Mind Maps
for
free
with GoConqr?
Learn more
.
Similar
Volcanoes
1jdjdjd1
Physics - Energy, Power & Work
dominique22
Application of technology in learning
Jeff Wall
A-level French Vocabulary
daniel.praecox
9 History- The Treaty of Versailles
melgallagher
BIOLOGY B1 3
x_clairey_x
IB Chem Flashcards
j. stu
Input, output and storage devices
Mr A Esch
General questions on photosynthesis
Fatima K
NSI Course
Yuvraj Sunar
Study tips/hacks
Sarah Biswas
Browse Library