Movatterモバイル変換

• Preface

• Introduction

• What's New

• Detailed Changes

• Clarifications

• Supported Platforms

• Downloading the Specification Documents

• Known Issues

• Product Information

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visithttp://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visithttp://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Oracle Welcomes Your Comments

Oracle is interested in improving its documentation and welcomes your comments and suggestions.

Please include the title of your document with your feedback:

Java Card Platform, v3.2, Classic Edition

Topics:

• What’s new in the Java Card Runtime Environment

• What's new in the Java Card API

Table - New Features in Java Card Virtual Machine Specifications

Table - New Features in Java Card API Specification

• A configuration where the Java Card Platform provides support for multiple logical channels. A terminal can open multiple logical channels over any I/O interface and assign each logical channel to an Applet instance. In this configuration, a platform may support the logical channels Type 4 encoding (logical channels 0 to 3) only or both the Type 4 and the Type 16 (logical channels 4 to 19) encodings.
• A configuration where the Java Card platform does not provide support for multiple logical channels. A terminal can only use the basic logical channel (logical channel 0) on each I/O interface and assign it to an Applet instance.

• A new derivation function algorithm is added to perform the HKDF-Expand-Label operation defined in RFC 8446 and to choose the label prefix either for TLS1.3 or for DTLS1.3.
• A new method is added to perform the transcript hash operation defined in RFC 8446: it is possible to perform an intermediate message digest calculation without changing the current state of the message digest instance and continue the operation.

• padding specified by ISO/IEC 9796-2 for signature scheme 1, signature production function B.6 and giving message recovery with a trailer field option 2.
• padding specified by ISO/IEC 9796-2 for signature scheme 2, signature production function B.6 and giving message recovery with a trailer field option 2.
• padding specified by ISO/IEC 9796-2 for signature scheme 3, signature production function B.6 and giving message recovery with a trailer field option 2.

3.1 Java Card Platform Virtual Machine Specification, Classic Edition, Version 3.2

3.1.1 6.16 Static Resource Component

• Fix typo:static_resource replaced bystatic_resource_info

3.2 Java Card API Specification, Classic Edition, Version 3.2

3.2.1 javacard.framework.MultiSelectable interface

• Method boolean select(boolean appInstAlreadyActive) – “package” replaced by “group context”. Clarify the behavior when multiple I/O interfaces are supported.
• Method void deselect(boolean appInstStillActive) – “package” replaced by “group context”. Clarify the behavior when multiple I/O interfaces are supported.

3.2.2 javacard.framework.APDU class

• Method byte getCLAChannel() – Clarify that the return value is based on the logical channel encoding type returned by APDU.getLogicalChannelEncoding().
• Method boolean isSecureMessagingCLA() – Clarify that the return value is based on the logical channel encoding type returned by APDU.getLogicalChannelEncoding().
• Method void setOutgoingLength(short len) – Clarify when APDUException.NO_T0_GETRESPONSE and APDUException.NO_T0_REISSUE are thrown when multiple I/O interfaces are supported.
• Method void sendBytesLong(byte[] outData, short bOff, short len) – Clarify when APDUException.NO_T0_GETRESPONSE is thrown when multiple I/O interfaces are supported.

3.2.3 javacard.framework.Applet class

• Method boolean select() – “package” replaced by “group context”. Clarify the behavior when multiple I/O interfaces are supported.
• Method void deselect() – “package” replaced by “group context”. Clarify the behavior when multiple I/O interfaces are supported.

3.2.4 javacard.framework.JCSystem class

• Method Shareable getAppletShareableInterfaceObject(AID serverAID, byte parameter) – Clarify the behavior when multiple I/O interfaces are supported.
• Method static boolean isAppletActive(AID theApplet) – Clarify the behavior when multiple I/O interfaces are supported.

3.2.5 javacard.framework.Resources class

• Method Resources getResources() – Clarify the returned instance is a permanent JCRE Entry Point Object that can be accessed from any applet context.
• Method byte[] getView(short resourceId, short ofs, short len) – Clarify that an IOException is thrown when the value offset + length exceeds the size returned by getSize().

3.2.6 javacard.security.ECKey interface

• Method void setK(short K) – Clarify that the value “1” must be supported by any implementation. A CryptoException.ILLEGAL_VALUE can be thrown when the cofactor value K is different from 1 and not supported by the platform.

3.2.7 javacard.security.GenericSecretKey interface

• Interface description – Clarify that the key can be of any length aligned on a multiple of 8 bits.

3.2.8 javacard.security.HMACKey interface

• Interface description – Clarify that the key can be of any length aligned on a multiple of 8 bits.

3.2.9 javacard.security.Key interface

• Method byte getType() – Clarify that KeyBuilder.TYPE_XEC is returned for keys implementing XECKey interface. Clarify that “0” is returned for keys for which the type is not one of the pre-defined algorithms.

3.2.10 Javacard.security.SignatureMessageRecovery interface

• Interface description – Clarify the list of algorithms used by Signature.getInstance(byte, boolean) and Signature.getInstance(byte, byte, byte, boolean) that return an instance implementing this interface.

3.2.11 javacard.security.InitializedMessageDigest class

• Method void setInitialDigest(byte[] state, short stateOffset, short stateLength, byte[] digestedMsgLenBuf, short digestedMsgLenOffset, short digestedMsgLenLength) – Correct typo “initalDigestLength” into “stateLength” when describing the CryptoException.ILLEGAL_VALUE case.

3.2.12 javacard.security.InitializedMessageDigest.OneShot class

• Method void setInitialDigest(…) – align parameters names with the same method described into the InitializedMessageDigest class.

3.2.13 javacard.security.KeyAgreement class

• Class description – Clarify preserved (e.g. key) and unpreserved instance values after a reset or a tear down.
• Constants ALG_EC_SVDP_DH, ALG_EC_SVDP_DHC – Clarify that those constants are deprecated and should be replaced respectively by ALG_EC_SVDP_DH_KDF and ALG_EC_SVDP_DHC_KDF.
• Constant ALG_SM2 – Clarify that it requires additional algorithm parameters and the use of the init(PrivateKey, AlgoritmParameterSpec) method.
• Method void init(PrivateKey privKey) – Clarify CryptoException.ILLEGAL_VALUE is thrown if KeyAgreement algorithm requires additional algorithm parameters.
• Method generateSecret(byte[] publicData, short publicOffset, short publicLength, byte[] secret, short secretOffset) – Clarify the preserved (e.g. key) and unpreserved instance values after generateSecret operation. CryptoException.UNINITIALIZED_KEY is thrown if the PrivateKey or any other key passed in additional parameters is not initialized. CryptoException.ILLEGAL_VALUE is thrown if the publicData data is inconsistent with the additional algorithm parameters passed in init(PrivateKey, AlgoritmParameterSpec). Clarify the return value and value length when ALG_SM2_WITH_CONFIRMATION algorithm is used.

3.2.14 javacard.security.KeyPair class

• Method void genKeyPair() – Clarify that, for DSA algorithm, default precomputed p, q and g parameters may be used by the platform if not provided by the application. It aligns with the Elliptic curve case.

3.2.15 javacard.security.RandomData class

• Method RandomData getInstance(byte algorithm) – This method is deprecated. getInstance(byte algorithm, boolean externalAccess) should be used instead.

3.2.16 javacard.security.Signature class

• Class description – Clarify the preserved (e.g. key and mode) and unpreserved instance values after a reset or a tear down.
• Constants ALG_RSA_SHA_ISO9796, ALG_RSA_RIPEMD160_ISO9796, ALG_RSA_SHA_ISO9796_MR, ALG_RSA_RIPEMD160_ISO9796_MR – Clarify constants refer to the scheme 1, the signature production function B.6 and trailer field option 1 of the ISO9796 specification.
• Constants ALG_RSA_SHA_PKCS1_PSS, ALG_RSA_MD5_PKCS1_PSS, ALG_RSA_RIPEMD160_PKCS1_PSS, ALG_RSA_SHA_224_PKCS1_PSS, ALG_RSA_SHA_256_PKCS1_PSS, ALG_RSA_SHA_384_PKCS1_PSS, ALG_RSA_SHA_512_PKCS1_PSS – Clarify the default salt length, the scheme digest algorithm and the MGF1 digest algorithm.
• Constants SIG_CIPHER_EDDSA, SIG_CIPHER_EDDSAPH – Clarify to which edDSA variants those constants refer to as per the RFC 8032. Clarify that this cipher algorithm must be associated with message digest algorithm MessageDigest.ALG_NULL and the padding algorithm Cipher.PAD_NULL when calling getInstance(byte, byte, byte, boolean).
• Method void init(Key theKey, byte theMode) – Remove the note about the default salt length value in case of RSA-PSS which is now decribed in the related RSA-PSS constants. Remove the note about “optimal performance”.
• Method init(Key theKey, byte theMode, byte[] bArray, short bOff, short bLen) – Remove the note about “optimal performance”. Clarify the expected behavior for managing RSA PSS and EDDSA Java Card Platform Specification Release Notes, v3.2 Page 23 parameters. CryptoException.NO_SUCH_ALGORITHM can be thrown if the parameters referenced in the byte array parameter are not supported in case of PAD_PKCS1_PSS_EXT_PARAMETERS padding.
• Method short getLength() – Clarify that for DSA and ECDSA, the returned length must be the maximum possible length of the related ASN.1 sequence.
• Method void setInitialDigest(…) – align parameters names with the same method described into the InitializedMessageDigest class.
• Method short sign(byte[] inBuff, short inOffset, short inLength, byte[] sigBuff, short sigOffset) – Clarify the preserved (e.g. key and mode) and unpreserved instance values after sign operation.
• Method short signPreComputedHash(byte[] hashBuff, short hashOffset, short hashLength, byte[] sigBuff, short sigOffset) – Clarify the preserved (e.g. key and mode) and unpreserved instance values after signPreComputedHash operation. Clarify CryptoException.ILLEGAL_USE is thrown for edDSA algorithm.
• Method boolean verify(byte[] inBuff, short inOffset, short inLength, byte[] sigBuff, short sigOffset, short sigLength) – Clarify the preserved (e.g. key and mode) and unpreserved instance values after verify operation.
• Method boolean verifyPreComputedHash(byte[] hashBuff, short hashOffset, short hashLength, byte[] sigBuff, short sigOffset, short sigLength) – Clarify the preserved (e.g. key and mode) and unpreserved instance values after verifyPreComputedHash operation. Clarify CryptoException.ILLEGAL_USE is thrown for edDSA algorithm.

3.2.17 javacard.security.Signature.OneShot class

• Method void setInitialDigest(…) – align parameter names with the same method described into the InitializedMessageDigest class.

3.2.18 javacardx.apdu.util.APDUUTIL class

• Method byte getCLAChannel(byte CLAbyte) – Clarify that this utility method always refer to the type APDU.LC_ENCODING_TYPE_4_TYPE_16.

3.2.19 javacardx.biometry.OwnerBioTemplate interface

• Method short initMatch(byte[] candidate, short offset, short length) – Clarify that the matching session ends in failed state if an exception is thrown during the match.
• Method short match(byte[] candidate, short offset, short length) – Clarify that the matching session ends in failed state if an exception is thrown during the match.

3.2.20 javacardx.biometry1toN.BioMatcher interface

• Method BioTemplateData getBioTemplateData(short index) – Clarify that template indexing starts at value « 1 » (« 0 » is an invalid value).
• Method short getIndexOfLastMatchingBioTemplateData() – Clarify that template indexing starts at value « 1 » (« 0 » is an invalid value).
• Method short initMatch(byte[] candidate, short offset, short length) – Clarify the matching session ends in failed state if an exception is thrown during the match. Also clarify that if the matching session ends, the validated flag remains in the reset state.
• Method short match(byte[] candidate, short offset, short length) – Clarify the matching session ends in failed state if an exception is thrown during the match. Also clarify that the matching session must ignore any enrolled BioTemplateData that is uninitialized. Bio1toNException.NO_BIO_TEMPLATE_ENROLLED is thrown if none of the enrolled BioTemplateData is initialized.

3.2.21 javacardx.biometry1toN.OwnerBioMatcher interface

• Method OwnerBioTemplateData getBioTemplateData(short index) – Clarify that template indexing starts at value « 1 » (« 0 » is an invalid value).
• Method short getIndexOfLastMatchingBioTemplateData() – Clarify that template indexing starts at value « 1 » (« 0 » is an invalid value).
• Method void putBioTemplateData(short index, BioTemplateData templateData) – Clarify that template indexing starts at value « 1 » (« 0 » is an invalid value).

3.2.22 javacardx.crypto.AEADCipher class

• Class description – Clarify the preserved (e.g. key and mode) and unpreserved instance values after a reset or a tear down.
• Method void init(Key theKey, byte theMode) – Remove references to non-AEAD algorithms. Clarify the nonce is a 12 bytes buffer full of zeroes for GCM mode.
• Method void init(Key theKey, byte theMode, byte[] bArray, short bOff, short bLen) – Remove references to non-AEAD algorithms.
• Method short update(byte[] inBuff, short inOffset, short inLength, byte[] outBuff, short outOffset) – Clarify the expected output length based on the algorithm. Add reference to array views case when input/output buffers overlap. Remove references to non-AEAD algorithms.
• Method short doFinal(byte[] inBuff, short inOffset, short inLength, byte[] outBuff, short outOffset) – Clarify the preserved (e.g. key and mode) and unpreserved instance values after doFinal operation. Remove references to non-AEAD algorithms.
• Method short retrieveTag(byte[] tagBuf, short tagOff, short tagLen) – Clarify CryptoException.ILLEGAL_USE is thrown if the mode is not MODE_ENCRYPT. Clarify CryptoException.ILLEGAL_VALUE if the tag length is not equal to the generated tag length e.g the length passed in init() method for ALD_AES_CCM.
• Method boolean verifyTag(byte[] receivedTagBuf, short receivedTagOff, short receivedTagLen, short requiredTagLen) – Fix typos: “bits” renamed in “bytes”. Clarify that if recievedTagLen and requiredTagLen are valid values and recievedTagLen < requiredTagLen, the method returns false. Clarify CryptoException.ILLEGAL_USE is thrown if the mode is not MODE_DECRYPT.

3.2.23 javacardx.crypto.Cipher class

• Class description – Clarify the preserved (e.g. key and mode) and unpreserved instance values after a reset or a tear down.
• Constants PAD_ISO9796, PAD_ISO9796_MR, PAD_ISO9796_MR_SCHEME_2, PAD_ISO9796_MR_SCHEME_3 – Clarify that these constants refer to the signature production function B.6 and trailer field option 1 of the ISO9796 specification.
• Constant PAD_PKCS1_PSS – Clarify default salt length, scheme digest algorithm and MGF1 digest algorithm.
• Constants ALG_RSA_PKCS1_OAEP, PAD_PKCS1_OAEP, PAD_PKCS1_OAEP_SHA224, PAD_PKCS1_OAEP_SHA256, PAD_PKCS1_OAEP_SHA384, PAD_PKCS1_OAEP_SHA512, PAD_PKCS1_OAEP_SHA3_224, PAD_PKCS1_OAEP_SHA3_256, PAD_PKCS1_OAEP_SHA3_384, PAD_PKCS1_OAEP_SHA3_512 – Clarify the scheme digest algorithm and the MGF1 digest algorithm.
• Method void init(Key theKey, byte theMode) – Remove the note about “optimal performance” and add reference to SM4.
• Method void init(Key theKey, byte theMode, byte[] bArray, short bOff, short bLen) – Remove the note about “optimal performance”. Clarify the input array format for AES XTS mode. Clarify the input array format for SM4 CBC mode. Clarify the expected behavior for managing RSA OAEP parameters. CryptoException.NO_SUCH_ALGORITHM can be thrown if the parameters referenced in the byte array parameter are not supported in case of PAD_PKCS1_OAEP_EXT_PARAMETERS padding.
• Method short update(byte[] inBuff, short inOffset, short inLength, byte[] outBuff, short outOffset) – Clarify the expected output length based on the algorithm. Add reference to array views case when input/output buffers overlap.
• Method short doFinal(byte[] inBuff, short inOffset, short inLength, byte[] outBuff, short outOffset) – Clarify preserved (e.g. key and mode) and unpreserved instance values after doFinal operation.

3.2.24 javacardx.security.derivation.DerivationFunction class

• Class description – Clarify that after a reset or a tear down, the object state is reset, like after a call to one of the nextBytes() methods, and has to be initialized again using the init(AlgorithmParameterSpec) method.

View the HTML files using any of the following CSS-compliant browsers:

• Internet Explorer, version 5.0 or later.
• Mozilla Firefox, version 11.0 or later.

View the PDF files in your web browser with an appropriate plugin or in the Adobe^® Acrobat Reader. Most recent browsers include the PDF reader plugin. However, if your browser doesn’t have one, then download the plugin from theInstall Adobe Acrobat Reader website.

• Product news and reviews
• Release notes and product documentation

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visithttp://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visithttp://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.