56
Java™
Java™
When running a Java™ application, you may be prompted to grant access to protected features. These features are protected
because using them could incur you cost, or involve your personal data. In case of doubt, don't hesitate to refuse access by
selecting the "No" button!
The security configuration menu is an expert feature! You must know exactly what you are doing before attempting to change
security parameters of a MIDlet. Misunderstanding changes may render MIDlet non functional and/or lead to higher risks for
your private data or impact your airtime consumption. Any changes in the security configuration are done under your
responsibility. In no case shall Sagem Communication and/or your network provider be liable for any damages deriving from
or arising out of such changes in the security configuration.
You must be aware that applications downloaded to your phone could cause the phone to perform actions for which you will
be billed, like making calls and sending SMS. Depending on your operator's billing policy, you may also be charged to
download the application because of airtime consumption.
Security considerations
Java™ MIDP technology is an efficient way to provide powerful applications in mobile phones.
All these MIDP 2.0 features cannot be simply exposed to any MIDlet installed in the handset: a careful access control system
is implemented in the device to protect your private data and airtime consumption.
Access controls are gathered in 9 security groups:
-
Network access
-
Auto invocation
-
Phone call
-
Local connectivity
-
Messaging receive
-
Messaging sending
-
Read User data
-
Write User data
-
Multimedia recording
Each of these security groups has one among 5 possible authorizations levels (listed from the more restrictive to the more
permissive):
-
Never: The security group completely prevents access to the protected features.
-
Per use: Each time MIDlet tries to use protected feature, user is prompted to grant access.
-
Per session: First time a MIDlet uses a protected function, user is prompted to grant access like in "Per use" authorization
but access is granted until the MIDlet terminates.
252693446_my500C-my501C_en.book Page 56 Mercredi, 21. juin 2006 3:06 15
Содержание MY5001C
Страница 1: ...252693446_my500C my501C_en book Page 1 Mercredi 21 juin 2006 3 06 15 ...
Страница 2: ...252693446_my500C my501C_en book Page 2 Mercredi 21 juin 2006 3 06 15 ...
Страница 11: ...Quick start Information on the SIM card 252693446_my500C my501C_en book Page 11 Mercredi 21 juin 2006 3 06 15 ...
Страница 16: ...Phonebook Using the phonebook 252693446_my500C my501C_en book Page 16 Mercredi 21 juin 2006 3 06 15 ...
Страница 33: ...Applications Music Player 252693446_my500C my501C_en book Page 33 Mercredi 21 juin 2006 3 06 15 ...
Страница 34: ...Applications see chapter Games Calendar 252693446_my500C my501C_en book Page 34 Mercredi 21 juin 2006 3 06 15 ...
Страница 37: ...Settings Phone settings 252693446_my500C my501C_en book Page 37 Mercredi 21 juin 2006 3 06 15 ...
Страница 47: ...Conformance Document 252693446_my500C my501C_en book Page 47 Mercredi 21 juin 2006 3 06 15 ...
Страница 48: ...252693446_my500C my501C_en book Page 48 Mercredi 21 juin 2006 3 06 15 ...
Страница 49: ...Care and safety information SAR 252693446_my500C my501C_en book Page 49 Mercredi 21 juin 2006 3 06 15 ...
Страница 67: ...252693446_my500C my501C_en book Page 67 Mercredi 21 juin 2006 3 06 15 ...
Страница 68: ...252693446_my500C my501C_en book Page 68 Mercredi 21 juin 2006 3 06 15 ...
Страница 69: ...252693446_my500C my501C_en book Page 69 Mercredi 21 juin 2006 3 06 15 ...
Страница 70: ...252693446_my500C my501C_en book Page 70 Mercredi 21 juin 2006 3 06 15 ...
Страница 71: ...252693446_my500C my501C_en book Page 71 Mercredi 21 juin 2006 3 06 15 ...
Страница 72: ...252693446_my500C my501C_en book Page 72 Mercredi 21 juin 2006 3 06 15 ...