In Symbian^3
Added SATSA-APDU support from Java Runtime 2.1 for Symbian onwards.
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 SATSA-CRYPTO.
Added support for SATSA-PKI.
In Series 40 6th Edition
No changes.
In Series 40 5th Edition
Added support for SATSA-CRYPTO.
In Series 40 3rd Edition Feature Pack 3
The SATSA implementation in Series 40 3rd Edition FP 3 is MSA (JSR-248) compliant.
In Series 40 3rd Edition Feature Pack 2
Series 40 3rd Edition FP 2 is the first release to support JSR-177.
Support for SATSA-APDU.