将Java AES/CBC/PKCS5PADDING加密逻辑迁移至Node.js的技术求助

Let's break down why your Node.js implementation isn't matching the Java code, then fix it step by step.

Key Mismatches Between Your Java and Node.js Code #

Your Java encryption logic is straightforward—it doesn’t use any key derivation function (like PBKDF2) at all. But your Node.js code is unnecessarily applying pbkdf2Sync, which creates a completely different key than what Java uses. Here are the exact gaps:

• Key Handling: Java takes the first 32 bytes of your key string directly as the AES-256 secret key. Your Node.js code is deriving a key via PBKDF2 with a salt and iterations, which isn’t present in Java.
• String Encoding: Java uses UTF-8 to convert the input string to bytes, but your Node.js code uses ASCII—this will corrupt non-ASCII characters.
• Redundant Parameter: The extra 'aes' parameter in your Node.js Buffer.from call for IV is unnecessary and can be removed for clarity.

Corrected Node.js Implementation #

Here’s the code that exactly mirrors your Java encryption logic:

const crypto = require('crypto');

function encryptPayload(value, key) {
  try {
    // Match Java's IV: first 16 bytes of the key string (UTF-8 encoded)
    const iv = Buffer.from(key.substring(0, 16), 'utf-8');
    // Match Java's secret key: first 32 bytes of the key string (UTF-8 encoded)
    const secretKey = Buffer.from(key.substring(0, 32), 'utf-8');
    // Algorithm matches Java's AES/CBC/PKCS5PADDING
    const cipher = crypto.createCipheriv('aes-256-cbc', secretKey, iv);
    
    // Use UTF-8 encoding to match Java's getBytes() behavior
    let encrypted = cipher.update(value, 'utf-8', 'base64');
    encrypted += cipher.final('base64');
    
    return encrypted;
  } catch (ex) {
    console.error('Encryption failed:', ex);
    return null;
  }
}

// Example usage
const secretKey = 'fgbnhgfcjhgfcvjkhgfcvjkhgfcvbjbnvcjhnbvcfghjnbvc';
const payload = 'Your target string to encrypt';
console.log(encryptPayload(payload, secretKey));

Explanation of Changes #

1. Removed PBKDF2: Since your Java code doesn’t use key derivation, we skip pbkdf2Sync entirely and directly use the raw bytes from your key string.
2. UTF-8 Encoding: Switched the input encoding in cipher.update from 'ascii' to 'utf-8' to align with Java’s default string-to-byte conversion.
3. Simplified IV Setup: Removed the redundant third parameter in Buffer.from—we only need to specify the encoding.
4. Consistent Error Handling: Added try/catch to mirror Java’s behavior of returning null on encryption failure.

This code will produce identical encrypted output to your Java encryptpayload method when given the same input string and key.

内容的提问来源于stack exchange，提问作者Asish Sharma