Motorola E680 Technical Manual - Page 95

Trusted MIDlet Suites Using x.509 PKI

Get Motorola E680 - Smartphone - GSM PDF manuals and user guides View all Motorola E680 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 95 highlights

21 MIDP 2.0 Security Model SMS send SMS receive Access phonebook Dial a call CBS Receive CBS Record audio/video Capture snapshot image Access File System "Send SMS?" "Receive SMS?" "Use Phonebook?" "Make Phone Call?" "Use CBS?" "Receive CBS?" "Record?" "Video capture?" "Using File?" The radio button messages will appear as follows and mapped to the permission types as shown in the table below: MIDP 2.0 Permission Types Blanket Session Oneshot No access Dialog Prompts "Always yes. Do not ask again." "Yes, this is running." "Only this operation. Ask me again." "Not this operation. Ask me again." "Not this running." "No, always denied. Do not ask again." The above runtime dialog prompts will not be displayed when the protected function is set to "Allowed" (or full access), or if that permission type is an option for that protected function according to the security policy table flexed in the handset. Trusted MIDlet Suites Using x.509 PKI Using the x.509 PKI (Public Key Infrastructure) mechanism, the handset will be able to verify the signer of the MIDlet suite and bind it to a protection domain which will allow the MIDlet suite access to the protected API or function. Once the MIDlet suite is bound to a protection domain, it will use the permission defined in the protection domain to grant the MIDlet suite access to the defined protected APIs or functions. The MIDlet suite is protected by signing the JAR file. The signature and certificates are added to the application descriptor (JAD) as attributes and will be used by the handset to verify the signature. Authentication is complete when the handset uses the root certificate (found on the handset) to bind the MIDlet suite to a protection domain (found on the handset). 95

  • 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
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
21
MIDP 2.0 Security Model
95
SMS send
“Send SMS?”
SMS receive
“Receive SMS?”
Access phonebook
“Use Phonebook?”
Dial a call
“Make Phone Call?”
CBS
“Use CBS?”
Receive CBS
“Receive CBS?”
Record audio/video
“Record?”
Capture snapshot image
“Video capture?”
Access File System
“Using File?”
The radio button messages will appear as follows and mapped to the permission types as
shown in the table below:
MIDP 2.0 Permission Types
Dialog Prompts
Blanket
“Always yes. Do not ask again.”
Session
“Yes, this is running.”
Oneshot
“Only this operation. Ask me again.”
“Not this operation. Ask me again.”
“Not this running.”
No access
“No, always denied. Do not ask again.”
The above runtime dialog prompts will not be displayed when the protected function is set
to “Allowed” (or full access), or if that permission type is an option for that protected
function according to the security policy table flexed in the handset.
Trusted MIDlet Suites Using x.509 PKI
Using the x.509 PKI (Public Key Infrastructure) mechanism, the handset will be able to
verify the signer of the MIDlet suite and bind it to a protection domain which will allow the
MIDlet suite access to the protected API or function. Once the MIDlet suite is bound to a
protection domain, it will use the permission defined in the protection domain to grant the
MIDlet suite access to the defined protected APIs or functions.
The MIDlet suite is protected by signing the JAR file. The signature and certificates are
added to the application descriptor (JAD) as attributes and will be used by the handset to
verify the signature. Authentication is complete when the handset uses the root certificate
(found on the handset) to bind the MIDlet suite to a protection domain (found on the
handset).