C#相当于Java RSA/ECB/OAEPTHHA-256和MGF1
我试图用Java加密字符串,用C#解密。 我先尝试了RSA/ECB/PKCS1PADDING,效果很好,但现在我尝试切换到OAEP填充,但我无法让它工作。加密工作正常,但解密工作不正常。我唯一更改的是Java中的算法名称,在C#中,我将rsa.Decrypt(data,true)从false更改为true。它需要更多的改变吗 我得到的异常是“解码OAEP填充时出错” 我的Java加密方法:C#相当于Java RSA/ECB/OAEPTHHA-256和MGF1,java,c#,cryptography,rsa,padding,Java,C#,Cryptography,Rsa,Padding,我试图用Java加密字符串,用C#解密。 我先尝试了RSA/ECB/PKCS1PADDING,效果很好,但现在我尝试切换到OAEP填充,但我无法让它工作。加密工作正常,但解密工作不正常。我唯一更改的是Java中的算法名称,在C#中,我将rsa.Decrypt(data,true)从false更改为true。它需要更多的改变吗 我得到的异常是“解码OAEP填充时出错” 我的Java加密方法: public byte[] rsaEncrypt(byte[] data) { byte[] c
public byte[] rsaEncrypt(byte[] data) {
byte[] cipherData;
try {
RSAPublicKeySpec keySpec = new RSAPublicKeySpec(pubMod, pubExp);
KeyFactory fact = KeyFactory.getInstance("RSA");
PublicKey pubKey = fact.generatePublic(keySpec);
Cipher cipher = Cipher.getInstance("RSA/ECB/OAEPWithSHA-256AndMGF1Padding");
cipher.init(Cipher.ENCRYPT_MODE, pubKey);
cipherData = cipher.doFinal(data);
return cipherData;
} catch (NoSuchAlgorithmException | IllegalBlockSizeException | InvalidKeyException | InvalidKeySpecException | NoSuchPaddingException | BadPaddingException e) {
e.printStackTrace();
}
return null;
}
private string RSADecrypt(byte[] data)
{
const string PrivateKey = *the key*;
const int PROVIDER_RSA_FULL = 1;
const string CONTAINER_NAME = "Tracker";
CspParameters cspParams;
cspParams = new CspParameters(PROVIDER_RSA_FULL);
cspParams.KeyContainerName = CONTAINER_NAME;
RSACryptoServiceProvider rsa = new RSACryptoServiceProvider(cspParams);
rsa.FromXmlString(PrivateKey);
byte[] decrypted = rsa.Decrypt(data, true);
String decryptedString = System.Text.Encoding.UTF8.GetString(decrypted);
return decryptedString;
}
我的C#解密方法:
public byte[] rsaEncrypt(byte[] data) {
byte[] cipherData;
try {
RSAPublicKeySpec keySpec = new RSAPublicKeySpec(pubMod, pubExp);
KeyFactory fact = KeyFactory.getInstance("RSA");
PublicKey pubKey = fact.generatePublic(keySpec);
Cipher cipher = Cipher.getInstance("RSA/ECB/OAEPWithSHA-256AndMGF1Padding");
cipher.init(Cipher.ENCRYPT_MODE, pubKey);
cipherData = cipher.doFinal(data);
return cipherData;
} catch (NoSuchAlgorithmException | IllegalBlockSizeException | InvalidKeyException | InvalidKeySpecException | NoSuchPaddingException | BadPaddingException e) {
e.printStackTrace();
}
return null;
}
private string RSADecrypt(byte[] data)
{
const string PrivateKey = *the key*;
const int PROVIDER_RSA_FULL = 1;
const string CONTAINER_NAME = "Tracker";
CspParameters cspParams;
cspParams = new CspParameters(PROVIDER_RSA_FULL);
cspParams.KeyContainerName = CONTAINER_NAME;
RSACryptoServiceProvider rsa = new RSACryptoServiceProvider(cspParams);
rsa.FromXmlString(PrivateKey);
byte[] decrypted = rsa.Decrypt(data, true);
String decryptedString = System.Text.Encoding.UTF8.GetString(decrypted);
return decryptedString;
}
似乎是SHA-256不适用于C。我将算法名称改为“RSA/ECB/OAEPWITHHA-1和MGF1PADDING”,它成功了 RSACryptServiceProvider不支持OAEP-SHA2 .NET 4.6添加了RSACng,它能够实现OAEP-SHA2(256384512)。NET 4.6还稍微更改了加密/解密和签名/验证签名,使其比布尔签名更具可扩展性,并将其移动到RSA基类:
using (RSA rsa = new RSACng())
{
rsa.FromXmlString(privateKeyXml);
byte[] decrypted = rsa.Decrypt(data, RSAEncryptionPadding.OaepSHA256);
return Encoding.UTF8.GetString(decrypted);
}
如果您的私钥来自X509Certificate2实例,则新方法(也在4.6中)将首选RSACng实例;虽然返回类型故意不保证。。。因此,如果您必须对其进行强制转换,则应使用
作为
而不是强制转换。如果有人知道原因,请随时发表评论!。MGF1中SHA-1的安全性不是问题,因此没有太多理由升级。