如何处理“AES/GCM/NoPadding"的 IV 和身份验证标签? [英] How are the IV and authentication tag handled for "AES/GCM/NoPadding"?

查看：44 发布时间：2022/1/10 9:52:14 java security encryption cryptography aes-gcm

本文介绍了如何处理“AES/GCM/NoPadding"的 IV 和身份验证标签?的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！

问题描述

我在 Java 8 中使用 AES/GCM/NoPadding 加密，我想知道我的代码是否存在安全漏洞.我的代码似乎工作，因为它可以加密和解密文本，但有一些细节不清楚.

I'm using AES/GCM/NoPadding encryption in Java 8 and I'm wondering whether my code has a security flaw. My code seems to work, in that it encrypts and decrypts text, but a few details are unclear.

我的主要问题是:

Cipher cipher = Cipher.getInstance("AES/GCM/NoPadding");
cipher.init(Cipher.ENCRYPT_MODE, key);
byte[] iv = cipher.getIV(); // ?????

该 IV 是否满足对于给定密钥，IV 不得重复"的要求.来自 RFC 4106?

我也很感谢我的相关问题的任何答案/见解(见下文)，但第一个问题最困扰我.我不知道在哪里可以找到回答这个问题的源代码或文档.

I'd also appreciate any answers / insight for my related questions (see below), but that first question is bugging me the most. I don't know where to find source code or documentation that answers this.

这里是完整的代码，大致.如果我在写这篇文章时引入了错误，我深表歉意:

Here is the full code, roughly. I apologize in case I introduced errors while writing this post:

class Encryptor {
  Key key;

  Encryptor(byte[] key) {
    if (key.length != 32) throw new IllegalArgumentException();
    this.key = new SecretKeySpec(key, "AES");
  }

  // the output is sent to users
  byte[] encrypt(byte[] src) throws Exception {
    Cipher cipher = Cipher.getInstance("AES/GCM/NoPadding");
    cipher.init(Cipher.ENCRYPT_MODE, key);
    byte[] iv = cipher.getIV(); // See question #1
    assert iv.length == 12; // See question #2
    byte[] cipherText = cipher.doFinal(src);
    assert cipherText.length == src.length + 16; // See question #3
    byte[] message = new byte[12 + src.length + 16]; // See question #4
    System.arraycopy(iv, 0, message, 0, 12);
    System.arraycopy(cipherText, 0, message, 12, cipherText.length);
    return message;
  }

  // the input comes from users
  byte[] decrypt(byte[] message) throws Exception {
    if (message.length < 12 + 16) throw new IllegalArgumentException();
    Cipher cipher = Cipher.getInstance("AES/GCM/NoPadding");
    GCMParameterSpec params = new GCMParameterSpec(128, message, 0, 12);
    cipher.init(Cipher.DECRYPT_MODE, key, params);
    return cipher.doFinal(message, 12, message.length - 12);
  }
}

假设用户破解我的密钥 = 游戏结束.

Suppose that users cracking my secret key = game over.

更详细的问题/相关问题:

More detailed questions / related questions:

cipher.getIV() 返回的 IV 以这种方式使用对我来说安全吗?

它是否避免了在 Galois/Counter 模式中重复使用 IV、组合键的灾难?
当我有多个应用程序同时运行此代码时仍然安全吗?所有应用程序都从同一 src 数据(可能在同一毫秒内)向用户显示加密消息?
返回的 IV 是由什么制成的?它是一个原子计数器加上一些随机噪声吗?
我是否需要避免 cipher.getIV() 并使用自己的计数器自己构造一个 IV?
假设我使用的是 Oracle JDK 8 + JCE Unlimited Strength 扩展，实现 cipher.getIV() 的源代码是否可以在线获得?

Does it avoid the catastrophe of reusing the IV,key combination in Galois/Counter Mode?
Is it still safe when I have multiple applications running this code at once, all displaying encrypted messages to users from the same src data (possibly in the same millisecond)?
What's the returned IV made of? Is it an atomic counter plus some random noise?
Do I need to avoid cipher.getIV() and construct an IV myself, with my own counter?
Is the source code implementing cipher.getIV() available online somewhere, assuming I'm using Oracle JDK 8 + JCE Unlimited Strength extension?

那个 IV 总是 12 字节长吗?

Is that IV always 12 bytes long?

身份验证标签是否总是 16 字节(128 位)长?

Is the authentication tag always 16 bytes (128 bits) long?

使用 #2 和 #3，并且没有填充，这是否意味着我的加密消息总是 12 + src.length + 16 字节长?(所以我可以安全地将它们压缩成一个字节数组，我知道正确的长度?)

With #2 and #3, and the lack of padding, does that mean my encrypted messages are always 12 + src.length + 16 bytes long? (And so I can safely squish them into one byte array, for which I know the correct length?)

在给定用户知道的恒定 src 数据的情况下，向用户显示无限数量的 src 数据加密是否安全?

Is it safe for me to display an unbounded number of src data encryptions to users, given constant src data that the users know?

如果 src 数据每次都不同(例如，包括 System.currentTimeMillis() 或随机数)，我向用户显示无限数量的 src 数据加密是否安全?

Is it safe for me to display an unbounded number of src data encryptions to users, if the src data is different every time (e.g. including System.currentTimeMillis() or random numbers)?

如果我在加密之前用随机数填充 src 数据会有帮助吗?在前面和后面说 8 个随机字节，还是只在一端?或者这根本没有帮助/让我的加密变得更糟?

Would it help if I padded the src data with random numbers before encryption? Say 8 random bytes in front and back, or only on one end? Or would that not help at all / make my encryption worse?

(因为这些问题都是关于我自己的代码的同一块，并且它们彼此密切相关，并且其他人在实现相同的功能时可能/应该有相同的问题集，因此拆分感觉是错误的问题分成多个帖子.如果这更适合 StackOverflow 的格式，我可以单独重新发布它们.让我知道！)

(Because these questions are all about the same block of my own code, and they are strongly related to each other, and others might/should have the same set of questions when implementing the same functionality, it felt wrong to split the questions into multiple posts. I can re-post them separately if that is more appropriate for StackOverflow's format. Let me know!)

如何处理“AES/GCM/NoPadding"的 IV 和身份验证标签? [英] How are the IV and authentication tag handled for "AES/GCM/NoPadding"?

问题描述

推荐答案

相关文章

Java开发最新文章

热门教程

热门工具

登录关闭

如何处理“AES/GCM/NoPadding"的 IV 和身份验证标签? [英] How are the IV and authentication tag handled for &quot;AES/GCM/NoPadding&quot;?

问题描述

推荐答案

相关文章

Java开发最新文章

热门教程

热门工具

登录 关闭

如何处理“AES/GCM/NoPadding"的 IV 和身份验证标签? [英] How are the IV and authentication tag handled for "AES/GCM/NoPadding"?

登录关闭