需要将 -Dcom.ibm.crypto.provider.DoRSATypeChecking=false
false改为true
详见:http://www-01.ibm.com/support/docview.wss?uid=swg1IV18625
APAR status
-
Closed as program error.
Error description
-
We have agreed to provide a flag for use at runtime to allow for the RSA encryption of data with the private key, as well as decryption of data with the public key. This flag can be set with the following property: -Dcom.ibm.crypto.provider.DoRSATypeChecking=false In Java 5, 6, 6.0_26, and 7, the default value will be "true" -- meaning that IBM's Java will have the old behavior. If this flag is set to "false" IBM's Java will allow for the atypical scenario with the reversal of the keys described above. Please note: This configuration is not recommended for use by developers of standard applications. It is understood that by setting this flag, a developer understands the behavior that is being enabled (encrypting with the private key/permitting anyone with the public key to decrypt). In nearly all cases, performing a signature in the standard way (with the private key to sign and the public key to verify) is preferred and recommended. With this APAR we are making sure the PUBLIC KEY can be used for DECRYPT.
Local fix
-
N/A
Problem summary
-
ERROR DESCRIPTION: IBM JVM should support encrypting using the private key and decrypting using the public key Note: This is a follow-up to APAR IV17344, which allows the public key to decrypt properly in this configuration
Problem conclusion
-
We have agreed to provide a flag for use at runtime to allow for the RSA encryption of data with the private key, as well as decryption of data with the public key. This flag can be set with the following property: -Dcom.ibm.crypto.provider.DoRSATypeChecking=false In Java 5, 6, 6.0_26, and 7, the default value will be "true" -- meaning that IBM's Java will have the old behavior. If this flag is set to "false" IBM's Java will allow for the atypical scenario with the reversal of the keys described above. Please note: This configuration is not recommended for use by developers of standard applications. It is understood that by setting this flag, a developer understands the behavior that is being enabled (encrypting with the private key/permitting anyone with the public key to decrypt). In nearly all cases, performing a signature in the standard way (with the private key to sign and the public key to verify) is preferred and recommended. Hursley defect: 190326. Affects ibmjceprovider.jar. Available in 5.0 SR 14, 6.0 SR11, 6.0_26 SR 3, and 7.0 SR 5 Jar build date: 20120404 WORKAROUNDS: None
相关推荐
gorsa 支持rsa公钥加密私钥解密;支持rsa公钥解密私钥加密
【delphiRSA加解密】支持RSA公钥加密私钥解密,RSA私钥加密公钥解密,秘钥格式支持PKCS8和PKCS1,D7~XE10可用
亲测可用,可参考:https://blog.csdn.net/qq_37835111/article/details/87358779
利用System.Numerics.BigInteger实现,私钥加密,公钥解密。兼容PKCS1填充方式。有效文件只有MyRSA.cs一个,其它文件是因为带了一个演示窗口。
用RSACryptoServiceProvider进行公钥解密时会出现“不正确的项”的错误,本类使用RSA PKCS#1 1.5的格式实现了公钥、私钥的双向加解密
rsa公钥解密程序,用于解密,使用的密钥格式见rsa密钥生成程序
基于.net的RSA私钥加密 公钥解密的源码--201903
asp.net RSA 私钥加密公钥解密 能解 php Java 实现RSA加密互通 ,PKCS#8 格式的的密钥文件 ,公钥解密 依赖于BouncyCastle.Crypto.dll
.net的RSA私钥加密 公钥解密的源码.net的RSA私钥加密 公钥解密的源码.net的RSA私钥加密 公钥解密的源码
基于openssl写的RSA的公钥加密,私钥解密,私钥加密,公钥解密的测试例子,密钥类型是rsa1024的PEM格式。
C# RSA私钥加密,公钥解密源码
PYTHON Crypto库支持RSA,私钥加密公钥解密, 文件名:RSA.PY 路径:Crypto\PublicKey\RSA.py 将此Crypto库中以上文件替换。 关于加解密方法看我的文章有写
采用RSA公钥加密体制,利用MFC写的界面程序
有朋友叫帮忙做有一个RSA加解密的帮助类,...由于C#RSA只支持公钥加密,私钥解密。而现在只能使用公钥加密,公钥解密,而且C#与Java并不互通,所以采用第三方类库 BouncyCastle来进行实现。并且实现了分段加密功能。
RSA非对称加解密算法,目前主流的加密算法,采用大数库生成大素数,然后根据算法原理,进行大数运算;算法在生成大素数时候相对耗时,但是在加解密的时候速度比较快,目前本算法支持512-2048位的加解密算法,并测试...
之前涉及到的RSA加解密都是用公钥加密私钥解密,看过此文档后你会发现原来公钥也可以用来解密啦,不同于数字签名哦
用于私钥加密 公钥解密用于私钥加密 公钥解密用于私钥加密 公钥解密
为需要的内容不多,主要是RSA加解密部分,所以就删除了不必要的,公钥私钥pem需要就用原来大佬的软件生成吧。(当然附件也打包了一份)。做了一些小修改,主要是演示 RSA有关 加密和解密 安全性的部分。公钥加密,...
虹软人脸识别 SDK+Demo;已实验好用,希望对你有帮助 的,包含人脸检测,人脸对比,人脸检索功能.
基于.net的RSA私钥加密 公钥解密的源码(0515).rar