In S60 5th Edition
Added SATSA-APDU support for S60 platform.
In S60 3rd Edition Feature Pack 2
The SATSA implementation in S60 3rd Edition FP2 is MSA (JSR 248) compliant.
Distinguished names can include escaped characters as defined
in RFC2253. However, only characters in ASN.1 PrintableString character set
are allowed. Other characters will result in IllegalArgumentException
.
In S60 3rd Edition Feature Pack 1
javax.microedition.securityservice.CMSMessageSignatureService
only
allows characters which can be found in the ASCII character set in caNames
.
In S60 3rd edition FP1, non-ASCII characters in caNames
cause IllegalArgumentException
.
Previously, in S60 3rd edition, having non-ASCII characters
in caNames
caused certificates not to be found, and thus CMSMessageSignatureServiceException
to
be thrown with reason code CRYPTO_NO_CERTIFICATE.
In S60 3rd Edition
Added support for handling OMA DRM 1.0 protected files.
Starting from S60 3rd Edition the root for common directories
is c:/data/
, whereas before S60 3rd Edition it was c:/nokia/
.
Starting from S60 3rd Edition the protected directory in
memory card is private/
, whereas before S60 3rd Edition
it was system/
.
Increased the size of the internal write buffer which speeded up the write operations to the memory card.
In Series 40 6th Edition
No changes.
In Series 40 5th Edition
The SATSA implementation in S40 5th Edition is MSA (JSR 248) compliant.
Support for the CRYPTO package added
In Series 40 3rd Edition Feature Pack 2
Series 40 3rd Edition FP2 is the first release to support JSR-177.