Re: Re: JCE cannot authenticate the provider BC - KeyStore

Hi,

about Signature SHA-1 vs. SHA-256: It's known that older software used 
SHA-1 cause SHA-256 just wasn't implemented. So, if you have recent 
stuff hashed with todays normal SHA-256/-384/-512 can't verified on 
older software cause they just implement SHA-2 algos.
Same issue caused recent Windows-Update to fail as M$ changed from SHA-1 
+ SHA-2 to SHA-2 only sign on update packages - but missed to previously 
update M$-update itself to use SHA-2. So, even SHA-2 is used for long 
time M$-update kept rely on SHA-1 as noone ever changed it after SHA-2 
was added.

Simple answer: Update to current OS/JVM.

Matt

Am 17.07.2019 um 16:07 schrieb luizurias:
> Hi,
>
> sorry, i made a mistake about the Cipher. It returns the same error when i
> try getInstance with BC provider.
>
> But, i tried with KeyPairGenerator and CertificateFactory and i dont get the
> error. Maybe because of this that you said about JCE policy..
>
> Btw, the only difference from this jar
> https://downloads.bouncycastle.org/misc/bcprov-jdk15on-1.62.jar from the
> official is that the jar signature was made using SHA1 and offical with
> SHA256?
>
>
>
>
>
> --
> Sent from: http://bouncy-castle.1462172.n4.nabble.com/Bouncy-Castle-Dev-f1462173.html
>