Closed GoogleCodeExporter closed 9 years ago
The issue was that the cert chain was only partially included with the request.
After this was changed by Bitpay, we get the following error:
java.security.cert.CertPathValidatorException: Version 1 certificates
can't be used as CA ones
I'm adding the cert chain again, this time as a file attachment.
+cc Kevin, because you wrote the original payment protocol implementation. Can
you say if we can fix this issue on the App/bitcoinj side?
Original comment by andreas....@gmail.com
on 14 Feb 2014 at 4:26
Attachments:
One way I can make it more robust is to fall back to the bitcoinj trust store
if the system store doesn't contain the cert we are looking for. That may or
may not solve the problem, but it would still be an improvement regardless.
Original comment by kgree...@gmail.com
on 16 Feb 2014 at 12:49
Oh I misunderstood the issue. Well here is the relevant code in the
CertPathValidator (search for "as CA ones"):
http://bouncycastle.sourcearchive.com/documentation/1.39/src_2org_2bouncycastle_
2jce_2provider_2PKIXCertPathValidatorSpi_8java-source.html
It explicitly throws that exception if the version of any of the certs in the
chain equals 1. I don't think there is anything we can do about it on the
bitcoinj side.
The problem is that the last cert in the attached cert chain is version 1.
Original comment by kgree...@gmail.com
on 16 Feb 2014 at 1:06
What's the issue about "version 1" certs? Can the issue be fixed by just
omitting that last cert?
BitPay already stated they won't change the root certificate anytime soon.
Original comment by andreas....@gmail.com
on 16 Feb 2014 at 9:14
I just tried Bitpay again, and the error message now is
"PaymentRequestException$PkiVerificationException: Invalid signature, this
payment request is not valid."
I'm not sure what they've been trying, I did not get an e-mail update yet.
Original comment by andreas....@gmail.com
on 16 Feb 2014 at 6:29
BitPay payment requests are validating for some time now. It must have been an
issue on their end.
Original comment by mh.in.en...@gmail.com
on 2 Mar 2014 at 12:01
Original issue reported on code.google.com by
andreas....@gmail.com
on 13 Feb 2014 at 8:44