Security
MIDP 1.0 used the “sandbox” security model,
similar to Applets, where MIDlets are only exposed to
“safe” APIs
MIDP 2.0 specifies how MIDlet Suites can be
cryptographically signed so that their authenticity and
origin can be validated
A new security framework is also specified such that
some “trusted” or “privileged” MIDlets, based on their
signature, can get access to APIs outside the sandbox,
which are not safe to expose to all MIDlets
For example, originating a phone call, using
the Push networking features, as well as
privileged features from future JSRs