-
Bug
-
Resolution: Won't Fix
-
P4
-
None
-
None
-
solaris
This only affects testing situations. No rational person uses all zero's in a real operation.
If the initialization vector is set to all zeros, Solaris ucrypto and pkcs11 libraries will return:
com.oracle.security.ucrypto.UcryptoException: CRYPTO_MECHANISM_PARAM_INVALID
at com.oracle.security.ucrypto.NativeCipher.nativeInit(Native Method)
at com.oracle.security.ucrypto.NativeGCMCipher.init(NativeGCMCipher.java:139)
at com.oracle.security.ucrypto.NativeGCMCipher.engineInit(NativeGCMCipher.java:214)
at javax.crypto.Cipher.init(Cipher.java:1394)
at javax.crypto.Cipher.init(Cipher.java:1327)
At this time there are no formalized specs restricting IV's. Until there is a spec, there is no need to follow Solaris's restrictions.
If the initialization vector is set to all zeros, Solaris ucrypto and pkcs11 libraries will return:
com.oracle.security.ucrypto.UcryptoException: CRYPTO_MECHANISM_PARAM_INVALID
at com.oracle.security.ucrypto.NativeCipher.nativeInit(Native Method)
at com.oracle.security.ucrypto.NativeGCMCipher.init(NativeGCMCipher.java:139)
at com.oracle.security.ucrypto.NativeGCMCipher.engineInit(NativeGCMCipher.java:214)
at javax.crypto.Cipher.init(Cipher.java:1394)
at javax.crypto.Cipher.init(Cipher.java:1327)
At this time there are no formalized specs restricting IV's. Until there is a spec, there is no need to follow Solaris's restrictions.
- relates to
-
JDK-8129567 CRYPTO_MECHANISM_PARAM_INVALID occurs if GCM mode parameter which is used as an IV is set to all zeros
- Closed