JDK13升级JDK16遇secp256r1曲线不支持 求BouncyCastle适配方案

该异常确实由JDK 16内置EC实现逻辑变更触发：JDK 16收紧了EC参数校验规则，而Google Tink 1.6.1版本默认优先调用JDK内置的KeyAgreement实现，不会主动匹配BouncyCastle生成的密钥参数格式，二者不兼容时就会抛出曲线不支持的报错。

不需要替换现有安全提供者，仅需要显式指定EC相关操作强制使用BouncyCastle实现即可，操作步骤如下：

1. 依赖校验 #

确认项目已正确引入对应版本依赖，Maven配置示例：

<dependencies>
    <dependency>
        <groupId>org.bouncycastle</groupId>
        <artifactId>bcprov-jdk15on</artifactId>
        <version>1.69</version>
    </dependency>
    <dependency>
        <groupId>com.google.crypto.tink</groupId>
        <artifactId>tink</artifactId>
        <version>1.6.1</version>
    </dependency>
</dependencies>

2. 业务代码调整 #

启动时优先注册BouncyCastle到安全提供者列表首位，ECDH密钥协商、密钥生成都显式指定BouncyCastle作为提供者，示例代码如下：

业务实现代码 #

import org.bouncycastle.jce.provider.BouncyCastleProvider;
import com.google.crypto.tink.subtle.EllipticCurves;
import java.security.Security;
import java.security.KeyPair;
import java.security.interfaces.ECPrivateKey;
import java.security.interfaces.ECPublicKey;

public class EcdhCryptoService {
    static {
        // 全局优先注册BouncyCastle安全提供者
        if (Security.getProvider(BouncyCastleProvider.PROVIDER_NAME) == null) {
            Security.insertProviderAt(new BouncyCastleProvider(), 1);
        }
    }

    // 生成secp256r1密钥对，指定BC提供者保证参数兼容
    public KeyPair generateSecp256r1KeyPair() throws Exception {
        java.security.KeyPairGenerator kpg = java.security.KeyPairGenerator.getInstance("EC", BouncyCastleProvider.PROVIDER_NAME);
        kpg.initialize(EllipticCurves.getNistP256Params().getParams());
        return kpg.generateKeyPair();
    }

    // 计算共享密钥，替换Tink默认实现，显式使用BC的ECDH实现
    public byte[] computeSharedSecret(ECPrivateKey privateKey, ECPublicKey publicKey) throws Exception {
        javax.crypto.KeyAgreement keyAgreement = javax.crypto.KeyAgreement.getInstance("ECDH", BouncyCastleProvider.PROVIDER_NAME);
        keyAgreement.init(privateKey);
        keyAgreement.doPhase(publicKey, true);
        return keyAgreement.generateSecret();
    }
}

单元测试用例 #

import org.junit.Test;
import java.security.KeyPair;
import java.security.interfaces.ECPrivateKey;
import java.security.interfaces.ECPublicKey;
import static org.junit.Assert.assertArrayEquals;

public class EcdhCryptoServiceTest {
    @Test
    public void testSharedSecretConsistency() throws Exception {
        EcdhCryptoService cryptoService = new EcdhCryptoService();
        // 生成通信双方密钥对
        KeyPair partyAKeyPair = cryptoService.generateSecp256r1KeyPair();
        KeyPair partyBKeyPair = cryptoService.generateSecp256r1KeyPair();
        // 双方分别计算共享密钥
        byte[] partyASecret = cryptoService.computeSharedSecret(
                (ECPrivateKey) partyAKeyPair.getPrivate(),
                (ECPublicKey) partyBKeyPair.getPublic()
        );
        byte[] partyBSecret = cryptoService.computeSharedSecret(
                (ECPrivateKey) partyBKeyPair.getPrivate(),
                (ECPublicKey) partyAKeyPair.getPublic()
        );
        // 校验两端生成的共享密钥完全一致
        assertArrayEquals(partyASecret, partyBSecret);
    }
}

你遇到的异常完整堆栈通常如下：

java.lang.IllegalArgumentException: Curve not supported: secp256r1 [NIST P-256,X9.62 prime256v1] (1.2.840.10045.3.1.7)
    at com.google.crypto.tink.subtle.EllipticCurves.computeSharedSecret(EllipticCurves.java:492)
    at com.yourbusiness.YourCryptoUtil.computeSharedSecret(YourCryptoUtil.java:68)
    at com.yourbusiness.EncryptionTest.testEcdh(EncryptionTest.java:24)
    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:78)
    at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.base/java.lang.reflect.Method.invoke(Method.java:567)
    at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
Caused by: java.security.InvalidKeyException: ECDH key agreement requires ECPublicKey for doPhase
    at jdk.crypto.ec/sun.security.ec.ECDHKeyAgreement.engineDoPhase(ECDHKeyAgreement.java:117)
    at java.base/javax.crypto.KeyAgreement.doPhase(KeyAgreement.java:579)
    at com.google.crypto.tink.subtle.EllipticCurves.computeSharedSecret(EllipticCurves.java:488)
	... 32 more

如果不想重写Tink的密钥协商逻辑，也可以直接将Tink升级到1.7.0及以上版本，该版本已适配JDK 16+的EC实现，默认会优先调用BouncyCastle的EC相关能力，无需手动修改业务代码。

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