如何用OpenSSL命令行实现与Java ECIESwithAES-CBC兼容的加密？

Alright, let's break down how to get OpenSSL's command-line ECIES encryption to match your Java/BouncyCastle code so the encrypted output is fully compatible for Java decryption.

First, let's map the key parameters from your Java code—these are the exact settings we need to replicate in OpenSSL:

• Algorithm: ECIESwithAES-CBC/NONE/PKCS7Padding
• Symmetric cipher: AES-CBC
• Padding: PKCS7
• MAC: Disabled (the NONE in your algorithm string means no message authentication code is added)
• KDF: BouncyCastle's default ECIES key derivation function (HKDF, typically paired with SHA-256)

Step 1: Prepare Your EC Public Key #

Your Java code reads an EC public key from a file—OpenSSL requires this key to be in PEM format. If you have a DER-formatted key, convert it first with this command:

openssl ec -in public_key.der -inform der -out public_key.pem -pubin

Step 2: Run the OpenSSL ECIES Encryption Command #

Use the ecencrypt command (available in OpenSSL 1.1.1+) with parameters that mirror your Java setup exactly:

openssl ecencrypt \
  -in data_to_encrypt.bin \
  -out encrypted_data.bin \
  -inkey public_key.pem \
  -pubin \
  -aes-128-cbc \
  -pkcs7padding \
  -kdf hkdf \
  -md sha256 \
  -mac none

Let's break down each critical parameter:

• -in: The input file containing your plaintext (matches the dataToEncrypt byte array in your Java code)
• -out: The output file with the encrypted data (matches the encryptedData byte array)
• -inkey/-pubin: Tells OpenSSL you're using a public key in PEM format
• -aes-128-cbc: Matches the AES-CBC symmetric cipher. Adjust this based on your EC curve:
  • P-256 → AES-128
  • P-384 → AES-192
  • P-521 → AES-256
• -pkcs7padding: Explicitly enables PKCS7 padding to align with your Java cipher configuration
• -kdf hkdf: Uses HKDF, which is BouncyCastle's default KDF for ECIES
• -md sha256: Matches BouncyCastle's default hash algorithm for HKDF. If your Java setup uses SHA-1 instead, replace this with -md sha1
• -mac none: Disables message authentication, matching the NONE component in your Java algorithm string

Step 3: Verify Compatibility #

To confirm everything works, test both directions:

1. Encrypt a file with OpenSSL, then decrypt it using your Java code (with the corresponding EC private key)
2. Encrypt data with your Java code, then decrypt it using OpenSSL's ecdecrypt command (mirroring the parameters above)

Troubleshooting Common Issues #

• Missing ecencrypt command: Upgrade to OpenSSL 1.1.1 or newer—older versions don't support this command
• Curve mismatch: Ensure your EC public key uses the same curve (e.g., P-256) in both Java and OpenSSL
• Encoding inconsistencies: If your Java code uses a specific string encoding (like UTF-8) to create dataToEncrypt, make sure your input file to OpenSSL uses the same encoding
• Decryption failures: Double-check that the KDF hash algorithm and MAC setting match exactly between Java and OpenSSL—even a small mismatch will break compatibility

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