Closed sylvainsf closed 9 years ago
Working with Bitcoin on Fedora is generally a problem all around due, in part, to it's hobbled OpenSSL binary with really limited (or no) ECC support. I believe it has something to do with questions concerning ECC patents. There are some third-party repo's that provide a complete OpenSSL implementation that may work or you could compile your own version of it with the correct crypto support.
What about posting to a rest api endpoint requires bitcoin crypto? On Aug 28, 2015 2:36 PM, "Rich Morgan" notifications@github.com wrote:
Working with Bitcoin on Fedora is generally a problem all around due, in part, to it's hobbled OpenSSL binary with really limited (or no) ECC support. I believe it has something to do with questions concerning ECC patents. There are some third-party repo's that provide a complete OpenSSL implementation that may work or you could compile your own version of it with the correct crypto support.
— Reply to this email directly or view it on GitHub https://github.com/bitpay/ruby-client/issues/47#issuecomment-135894206.
BitPay's cryptographically-secure API uses the same ECC to create asymmetric keypairs and digital signatures for requests issued to non-public API endpoints. Without the base crypto support to create these keys and signatures, calling anything other than public endpoints won't work.
SDK is unable to establish any client connections from Fedora/RHEL/CentOS hosts due to the curve used for keys/signing.