You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@santuario.apache.org by "Kevin Urciolo (JIRA)" <ji...@apache.org> on 2014/08/15 22:11:20 UTC
[jira] [Updated] (SANTUARIO-396) XMLCipher does not allow the use
of Entrust RSAOAEPParamterSpec for RSA OAEP
[ https://issues.apache.org/jira/browse/SANTUARIO-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Urciolo updated SANTUARIO-396:
------------------------------------
Description:
Similar to SANTUARIO-392, an Entrust FIPS compliant security provider for JAVA requires a RSAOAEPParameterSpec for RSA OAEP. This prevents encryption from working since XMLCipher doesn't appear to generate this parameter spec. Since this class is Entrust specific, it might be a good idea to allow pluggable parameter specs by algorithm URL.
Original Exception was java.security.InvalidKeyException: Invalid parameters for an RSA cipher; only RSAOAEPParameterSpec is supported
at org.apache.xml.security.encryption.XMLCipher.encryptKey(XMLCipher.java:1443)
at org.apache.xml.security.encryption.XMLCipher.encryptKey(XMLCipher.java:1382)
was:
Similar to SANTUARIO-392, an Entrust FIPS compliant security provider for JAVA uses requires a RSAOAEPParameterSpec for RSA OAEP. This prevents encryption from working since XMLCipher doesn't appear to generate this parameter spec. Since this class is Entrust specific, it might be a good idea to allow pluggable parameter specs by algorithm URL.
Original Exception was java.security.InvalidKeyException: Invalid parameters for an RSA cipher; only RSAOAEPParameterSpec is supported
at org.apache.xml.security.encryption.XMLCipher.encryptKey(XMLCipher.java:1443)
at org.apache.xml.security.encryption.XMLCipher.encryptKey(XMLCipher.java:1382)
> XMLCipher does not allow the use of Entrust RSAOAEPParamterSpec for RSA OAEP
> ----------------------------------------------------------------------------
>
> Key: SANTUARIO-396
> URL: https://issues.apache.org/jira/browse/SANTUARIO-396
> Project: Santuario
> Issue Type: Bug
> Components: Java
> Affects Versions: Java 1.5.7, Java 2.0.1
> Environment: Using Entrust etjava80_8.0_Patch_190183 with Santuario 1.5.7. Compatibility problems between two products when attempting to encrypt using Entrust security provider with RSA OAEP.
> Reporter: Kevin Urciolo
> Assignee: Colm O hEigeartaigh
>
> Similar to SANTUARIO-392, an Entrust FIPS compliant security provider for JAVA requires a RSAOAEPParameterSpec for RSA OAEP. This prevents encryption from working since XMLCipher doesn't appear to generate this parameter spec. Since this class is Entrust specific, it might be a good idea to allow pluggable parameter specs by algorithm URL.
> Original Exception was java.security.InvalidKeyException: Invalid parameters for an RSA cipher; only RSAOAEPParameterSpec is supported
> at org.apache.xml.security.encryption.XMLCipher.encryptKey(XMLCipher.java:1443)
> at org.apache.xml.security.encryption.XMLCipher.encryptKey(XMLCipher.java:1382)
--
This message was sent by Atlassian JIRA
(v6.2#6252)