Motorola E680 Technical Manual - Page 94

Implementation based on Recommended Security, Policy, Trusted 3, Party Domain

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 94 highlights

• oneshot - will prompt the user each time the protected API or function is requested by the MIDlet suite. (Always Ask) • No - will not allow the MIDlet suite access to the requested API or function that is protected. (No Access) The prompt No, Ask Later will be displayed during runtime dialogs and will enable the user to not allow the protected function to be accessed this instance, but to ask the user again the next time the protected function is called. User permission interaction modes will be determined by the security policy and device implementation. User permission will have a default interaction mode and a set of other available interaction modes. The user should be presented with a choice of available interaction modes, including the ability to deny access to the protected API or function. The user will make their decision based on the user-friendly description of the requested permissions provided for them. The Permissions menu allows the user to configure permission settings for each MIDlet when the VM is not running. This menu is synchronized with available run-time options. Implementation based on Recommended Security Policy The required trust model, the supported domain, and their corresponding structure will be contained in the default security policy for Motorola's implementation for MIDP 2.0. Permissions will be defined for MIDlets relating to their domain. User permission types, as well as user prompts and notifications, will also be defined. Trusted 3rd Party Domain A trusted third party protection domain root certificate is used to verify third party MIDlet suites. These root certificates will be mapped to a location on the handset that cannot be modified by the user. The following table shows the specific wording to be used in the first line of the above prompt: Protected Functionality Data network Data network (server mode) Comm Push SMS Top Line of Prompt "Send Data?" "Receive Data?" "Connect?" "Auto Start-Up?" "Use SMS?" 94

  • 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
94
•
oneshot – will prompt the user each time the protected API or function is
requested by the MIDlet suite. (
Always Ask
)
•
No – will not allow the MIDlet suite access to the requested API or function that is
protected. (
No Access
)
The prompt
No, Ask Later
will be displayed during runtime dialogs and will enable the
user to not allow the protected function to be accessed this instance, but to ask the user
again the next time the protected function is called.
User permission interaction modes will be determined by the security policy and device
implementation. User permission will have a default interaction mode and a set of other
available interaction modes. The user should be presented with a choice of available
interaction modes, including the ability to deny access to the protected API or function.
The user will make their decision based on the user-friendly description of the requested
permissions provided for them.
The Permissions menu allows the user to configure permission settings for each MIDlet
when the VM is not running. This menu is synchronized with available run-time options.
Implementation based on Recommended Security
Policy
The required trust model, the supported domain, and their corresponding structure will be
contained in the default security policy for Motorola’s implementation for MIDP 2.0.
Permissions will be defined for MIDlets relating to their domain. User permission types, as
well as user prompts and notifications, will also be defined.
Trusted 3
rd
Party Domain
A trusted third party protection domain root certificate is used to verify third party MIDlet
suites. These root certificates will be mapped to a location on the handset that cannot be
modified by the user.
The following table shows the specific wording to be used in the first line of the above
prompt:
Protected Functionality
Top Line of Prompt
Data network
“Send Data?”
Data network (server mode)
“Receive Data?”
Comm
“Connect?”
Push
“Auto Start-Up?”
SMS
“Use SMS?”