sslcontext-kickstart: org.bouncycastle.pkcs.PKCSException
Describe the bug
i use permUtil to load the perm certificate, a Exception was thrown
To Reproduce
X509ExtendedKeyManager keyManager = PemUtils.parseIdentityMaterial(certificate.getCertificate(), certificate.getPrivateKey(), certificate.getPassphrase().toCharArray());
the error is
Caused by: org.bouncycastle.pkcs.PKCSException: unable to read encrypted data: 1.2.840.113549.1.5.13 not available: Wrong algorithm: AES or Rijndael required
at org.bouncycastle.pkcs.PKCS8EncryptedPrivateKeyInfo.decryptPrivateKeyInfo(Unknown Source)
at nl.altindag.ssl.decryptor.BouncyFunction.lambda$andThen$0(BouncyFunction.java:22)
at nl.altindag.ssl.util.PemUtils.extractPrivateKeyInfo(PemUtils.java:493)
... 55 common frames omitted
Caused by: org.bouncycastle.operator.OperatorCreationException: 1.2.840.113549.1.5.13 not available: Wrong algorithm: AES or Rijndael required
at org.bouncycastle.openssl.jcajce.JceOpenSSLPKCS8DecryptorProviderBuilder$1.get(Unknown Source)
... 58 common frames omitted
Caused by: java.security.InvalidKeyException: Wrong algorithm: AES or Rijndael required
at com.sun.crypto.provider.AESCrypt.init(AESCrypt.java:83)
at com.sun.crypto.provider.CipherBlockChaining.init(CipherBlockChaining.java:93)
at com.sun.crypto.provider.CipherCore.init(CipherCore.java:591)
at com.sun.crypto.provider.CipherCore.init(CipherCore.java:619)
at com.sun.crypto.provider.AESCipher.engineInit(AESCipher.java:355)
at javax.crypto.Cipher.implInit(Cipher.java:810)
at javax.crypto.Cipher.chooseProvider(Cipher.java:864)
at javax.crypto.Cipher.init(Cipher.java:1539)
at javax.crypto.Cipher.init(Cipher.java:1470)
... 59 common frames omitted
JDK version: Java™ SE Runtime Environment (build 1.8.0_131-b11) System: Ubuntu SMP Fri Aug 10 11:14:32 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
however this is ok when using jdk1.8.0_291.jdk
what should i do when using jdk 1.8.0_131-b11?
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 28 (12 by maintainers)
i have find a way to deal this: looks like 128bit or 256 bit problem
but i still busying with finding the way to solve this with code rather than update jar in jdk.
as for code way, i think you guys are better at with code