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

cryptearth <[email protected]> Tue, 16 Jul 2019 21:41:07 +0200
Newsgroups gmane.comp.encryption.bouncy-castle.devel
Message-ID <[email protected]>
Hi,

I remerged the answers to keep the list in-sync - nvm.

I given up to even try to ask people why they keep at such old versions 
- I made my guesses and unless it's one of them the most obvious reason: 
someone higher the payment list not know about upgrade and just refuse 
needed resources to do it although it mostly saves more money to invest 
once in the upgrade in the long term - nvm.

About the "random" issue: my wild guess is that it's maybe only some of 
the signatures' corrupted. I don't know if a security jar has to verify 
completly or just the classes in use - but if the whole jar fail due to 
one issue none of it would work at all - so as it works at least 
somewhat only the per-class-in-use signature lasts as a possible option. 
As I discovered a wired crypto bug in j9 and j10 I guess the whole 
security card house is so briddle we're lucky if it at least sometimes 
works like RFCs say so.

Matt

Am 16.07.2019 um 21:29 schrieb luizurias:
> Yes, i know i am using outdaded java. I really want to update but for now i
> cant.
>
> Anyways, thanks for you reply!
>
> It worked! Thanks.
>
> But i still dont undestand why it is only occurring with KeyStore
> operations, i mean if i initialize a Cipher with BC provider and realize
> some operations the error does not occur. Do you know why?
>
> --
> Sent from: http://bouncy-castle.1462172.n4.nabble.com/Bouncy-Castle-Dev-f1462173.html
>