gpt4 book ai didi

java - AEADBadTagException 标签与套接字数据不匹配

转载 作者:行者123 更新时间:2023-12-02 00:59:44 25 4
gpt4 key购买 nike

我有一个服务器,让套接字连接到它以通过输入流发送数据,该数据在名为 Cryptoographer 的类中使用 AES/GCM/NoPadding 进行加密。服务器具有保存连接客户端功能的线程,每个线程都在 ConnectionThread 类中表示,该类保存对在服务器类中初始化的密码器类的引用。

问题:

当我发送第一个命令时,它工作得很好,没有任何问题。但不知何故,当我发送第二个命令时,如果给出以下堆栈跟踪:

javax.crypto.AEADBadTagException: Tag mismatch!
at java.base/com.sun.crypto.provider.GaloisCounterMode.decryptFinal(GaloisCounterMode.java:595)
at java.base/com.sun.crypto.provider.CipherCore.finalNoPadding(CipherCore.java:1116)
at java.base/com.sun.crypto.provider.CipherCore.fillOutputBuffer(CipherCore.java:1053)
at java.base/com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:853)
at java.base/com.sun.crypto.provider.AESCipher.engineDoFinal(AESCipher.java:446)
at java.base/javax.crypto.Cipher.doFinal(Cipher.java:2208)
at com.company.security.Cryptographer.decrypt(Cryptographer.java:53)
at com.company.client.Reader.run(Reader.java:45)
at java.base/java.lang.Thread.run(Thread.java:835)
Exception in thread "Thread-3" java.lang.NullPointerException
at java.base/java.lang.String.<init>(String.java:623)
at com.company.client.Reader.run(Reader.java:47)
at java.base/java.lang.Thread.run(Thread.java:835)

这些是堆栈跟踪中提到的类

密码学家

package com.company.security;

import javax.crypto.*;
import javax.crypto.spec.GCMParameterSpec;
import javax.crypto.spec.SecretKeySpec;
import java.security.InvalidAlgorithmParameterException;
import java.security.InvalidKeyException;
import java.security.Key;
import java.security.NoSuchAlgorithmException;
import java.util.Base64;

public class Cryptographer {
private Key secretKey;
private GCMParameterSpec gcmParameterSpec;

public Cryptographer() {
byte[] secret = new byte[16]; // 128 bit is 16 bytes, and AES accepts 16 bytes, and a few others.
byte[] secretBytes = "secret".getBytes();
byte[] IV = new byte[12];
gcmParameterSpec = new GCMParameterSpec(16 * 8, IV);
System.arraycopy(secretBytes, 0, secret, 0, secretBytes.length);
secretKey = new SecretKeySpec(secret, "AES");
}

/**
* Encrypt data.
* @param data to encrypt
* @return encrypted data
*/
public byte[] encrypt(byte[] data) {
try {
Cipher cipher = Cipher.getInstance("AES/GCM/NoPadding");
cipher.init(Cipher.ENCRYPT_MODE, secretKey, gcmParameterSpec);
byte[] encrypted = cipher.doFinal(data);
return encrypted;
} catch (InvalidKeyException | BadPaddingException
| IllegalBlockSizeException | NoSuchPaddingException
| NoSuchAlgorithmException | InvalidAlgorithmParameterException e) {
e.printStackTrace();
return null;
}
}

/**
* Decrypt data.
* @param data to decrypt
* @return decrypted data
*/
public byte[] decrypt(byte[] data) {
try {
Cipher cipher = Cipher.getInstance("AES/GCM/NoPadding");
cipher.init(Cipher.DECRYPT_MODE, secretKey, gcmParameterSpec);
return cipher.doFinal(data);
} catch (InvalidKeyException | BadPaddingException
| IllegalBlockSizeException | NoSuchPaddingException
| NoSuchAlgorithmException | InvalidAlgorithmParameterException e) {
e.printStackTrace();
return null;
}
}
}

阅读器

package com.company.client;

import com.company.FileLoader;
import com.company.client.helpers.ClientFileHelper;
import com.company.client.workers.MessageSender;
import com.company.security.Cryptographer;

import java.io.BufferedReader;
import java.io.IOException;
import java.io.InputStream;

public class Reader implements Runnable {
private InputStream inputStream;
private ClientFileHelper fileHelper;
private Cryptographer cryptographer;
private FileLoader fileLoader;
private BufferedReader bufferedReader;
private MessageSender messageSender;
private boolean isActive = true;
private boolean isReceivingFile = false;


public Reader(BufferedReader bufferedReader, MessageSender messageSender, InputStream inputStream) {
this.bufferedReader = bufferedReader;
this.messageSender = messageSender;
this.inputStream = inputStream;
cryptographer = new Cryptographer();
}

@Override
public void run() {
while (isActive) {
try {
int count;
byte[] buffer;

if(!isReceivingFile) {
buffer = new byte[inputStream.available()];
} else {
buffer = new byte[inputStream.available()];
}

while ((count = inputStream.read(buffer)) > 0)
{
byte[] decrypted = cryptographer.decrypt(buffer);
if(!isReceivingFile) {
handleInput(new String(decrypted));
} else {
if(fileHelper.getFileBytes().length == 0) {
fileHelper.setFileBytes(decrypted);
} else {
fileHelper.saveFile();
isReceivingFile = false;
}
}
}
} catch (IOException e) {
e.printStackTrace();
break;
}
}

}

/**
* Handle the user input form the console.
* @param input user input from console
*/
private void handleInput(String input) {
try {
if (input.equals("PING")) { // If we get a PING message we send back a PONG message.
messageSender.send("PONG");
} else if (input.contains("FILE")) {
setupFileAccept(input);
isReceivingFile = true;
} else {
System.out.println(input);
}
} catch (Exception ex) {
isActive = false;
}
}

/**
* Setup the file helper for the client that's going to receive a file.
* @param line command
*/
private void setupFileAccept(String line) {
String[] args = line.split(" ");
if(args[0].equals("FILE")) {
fileHelper = new ClientFileHelper(args[1], Integer.valueOf(args[2]));
}
}
}

ConnectionThread 也有类似的读取功能,如下所示:

while (isActive) {
try {
int count;
byte[] buffer;

if(!isReceivingFile) {
buffer = new byte[inputStream.available()];
} else {
buffer = fileHelper.getFileBytes();
}

while ((count = inputStream.read(buffer)) > 0)
{
byte[] decrypted = server.cryptographer.decrypt(buffer);
if(!isReceivingFile) {
getInput(new String(decrypted));
} else {
fileHelper.setFileBytes(decrypted);
// bytes received, now we can send the file!
if(fileHelper.sendToReceiver()) {
writeToClient(fileHelper.getReceiverName()
+ " received " + fileHelper.getFilename());
fileHelper = null;
}
}
}
} catch (IOException e) {
e.printStackTrace();
break;
}
}

在这种情况下,只需假设 Server 类具有正确初始化的 cryptoographer 属性,情况总是如此。

我的猜测是某个值在某个地方做错了事情,但我不确定。我对应该做什么来解决这个问题一无所知。有人可以帮我指出错误并提出可能的解决方案来解决这个问题吗?我的java版本是12.0.1

最佳答案

我鼓励考虑使用 SSL/TLS 或 DTLS,而不是尝试重新实现其中的一部分。

我不确定它是否会导致您的错误,但如果我对 Java documentation 的解释是否如此是正确的,您应该更改每条消息的 GCMParameterSpec:

after each encryption operation using GCM mode, callers shouldre-initialize the cipher objects with GCM parameters which has adifferent IV value

和:

GCM mode has a uniqueness requirement on IVs used in encryption with a given key. When IVs are repeated for GCM encryption, such usages are subject to forgery attacks.

此外,您没有使用 updateAAD(附加身份验证数据),尽管根据 https://www.rfc-editor.org/rfc/rfc5084 这是可选的从错误消息来看,这似乎是它导致了错误,但它可能只是一个误导性的错误消息。

更新:

我为 Cryptoographer 类编写了大量单元测试,只有在再次解密之前开始对密文进行随机更改时,我经常会遇到相同的错误。因为我们可以信任 TCP/IP 在连接的另一端重现完全相同的字节,所以我们可能会遇到此类问题:

  1. 并发
  2. 将密文字节转换为字符串、字符、读取器/写入器
  3. 没有从套接字读取整个消息(您是否检查过发送的字节数并将其与收到的字节数进行比较?

不,我还没有编写和测试我自己的实现,但是有一些例子,比如 this example , nicely explained by the author here来自the code was found by this search

关于java - AEADBadTagException 标签与套接字数据不匹配,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/60822488/

25 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com