Re: JCE cannot authenticate the provider BC - KeyStore

Hi,

security providers have to be signed by a trusted key. As you say this 
issue occur after update from 1.60 to 1.61 it's most likely the signing 
key changed wich isn't trusted by a key that's in 6_45. I use 1.62 with 
Oracle 8_144 and 8_212 - works fine. Btw: It's June 2019 - why you still 
use Java 6? Only reason would be a very old and most likely out-dated OS 
- wich also hints very old hardware - so I guess you either have some 
embedded industry system - or someone up the chain doesn't allow upgrade 
to recent hardware/software. So, instead of blame a lib for obvious 
reason (way out-dated runtime don't have master-key to verify current 
sign key) consider why you use 10 year old stuff and why you not upgrade it.

Matt

Am 15.07.2019 um 21:57 schrieb luizurias:
> Hello,
>
> After i updated BC from 1.60 to 1.61 (occurs in 1.62 too) i am getting this
> error. It only occurs with KeyStore, when i use the BC provider for others
> operations (such as Cipher, etc..) i dont get this error. And in version
> 1.60 works fine.
>
> I already tried to add the bc-*.jar in the jre/lib/ext but the error
> continues
>
> Of course this dont happen when i use OpenJDK. I am using Oracle JDK 1.6_45.
>
> Has anyone ever had anything like it or know what is going on?
>
> Caused by: java.io.IOException: error constructing MAC:
> java.lang.SecurityException: JCE cannot authenticate the provider BC
> 	at
> org.bouncycastle.jcajce.provider.keystore.pkcs12.PKCS12KeyStoreSpi.engineLoad(Unknown
> Source)
> 	at java.security.KeyStore.load(Unknown Source)
>
>
>
> --
> Sent from: http://bouncy-castle.1462172.n4.nabble.com/Bouncy-Castle-Dev-f1462173.html
>