AES 128 DOT NET 和 Java 兼容性

发布于 2024-10-04 04:36:08 字数 1001 浏览 0 评论 0原文

我们一直在尝试一种方案的原型，在该方案中我们在两个系统之间加密解密数据：一个在 .NET 中，另一个在 Java 中。我们将使用简单的 128 位 AES 加密。

我面临的问题很微不足道，但我找不到合适的解决方案。也许我对 AES 或加密的理解总体上较少。

假设我们有一个预定义的密钥，由以下十六进制字符串表示：“9c361fec3ac1ebe7b540487c9c25e24e”。这是一个 16 字节的密钥。 Java 中的加密部分是

  final byte[] rawKey = hexStringToByteArray("9c361fec3ac1ebe7b540487c9c25e24e");
  final SecretKeySpec skeySpec = new SecretKeySpec(rawKey, "AES");
  // Instantiate the cipher
  final Cipher cipher = Cipher.getInstance("AES");
  cipher.init(Cipher.ENCRYPT_MODE, skeySpec);

  final byte[] encrypted = cipher.doFinal(plainText.getBytes());

“hexStringToByteArray”函数将十六进制字符串转换为字节数组。问题是在java中，字节是有符号的。因此值 9C 是 -100 而不是 156（在 .NET 中是这样）。

Java 中，这变为： -100,54,31,-20,58,-63,-21,-25,-75,64,72,124,-100,37,-30,78

在然而，.NET 是： 156,54,31,236,58,193,235,231,181,64,72,124,156,37,226,78

问题：鉴于密钥本身的表示不同，它会影响加密过程本身吗？这是没有 CBC 和 PADDING 的简单加密。

编辑：更新了代码以使其看起来格式化。

原文

We have been trying a prototype of a scheme where we encrypt decrypt data between two systems: One in .NET and the other in Java. We were going to use simple 128 bit AES Encryption.

The problem I am facing is trivial, but I cannot find a proper solution. Maybe my understanding of AES or Encryption in general is less.

Assuming we have a predefined key, represented by the following hex string: "9c361fec3ac1ebe7b540487c9c25e24e".
This is a 16-byte key.
The encryption part in Java would be

  final byte[] rawKey = hexStringToByteArray("9c361fec3ac1ebe7b540487c9c25e24e");
  final SecretKeySpec skeySpec = new SecretKeySpec(rawKey, "AES");
  // Instantiate the cipher
  final Cipher cipher = Cipher.getInstance("AES");
  cipher.init(Cipher.ENCRYPT_MODE, skeySpec);

  final byte[] encrypted = cipher.doFinal(plainText.getBytes());

The 'hexStringToByteArray' function converts the hex string to a byte array. The problem is that in java, bytes are signed. So the value 9C is -100 and not 156 (as it would be in .NET).

In Java this becomes: -100,54,31,-20,58,-63,-21,-25,-75,64,72,124,-100,37,-30,78

In .NET however, this is: 156,54,31,236,58,193,235,231,181,64,72,124,156,37,226,78

Question:
Given that the representation of the keys itself differs, would it affect the encryption process itself?
This is simple encryption without CBC and PADDING.

Edit: Updated the code to look formatted.

分享到QQ

分享到微博