OpenSSL and EC Libraries: Difference between revisions

From Bitcoin Wiki
Jump to navigation Jump to search
Andytoshi (talk | contribs)
Clarify bitcoin's non-use of restricted algos, don't be dismissive of heartbleed
934 (talk | contribs)
→‎Fixes / Workarounds: remove outdated "RPMs provided by gmaxwell". fedora up to version 21 does not even receive security updates, not to mention the bugs in openssl... Save not to link to those rpms imo
Line 5: Line 5:
== Fixes / Workarounds ==
== Fixes / Workarounds ==


Some fixes are


* Compile your own OpenSSL and use this rather than the distribution package manager's library.
One workaround is to compile your own OpenSSL and use this rather than the distribution package manager's library.
* Use the RPMs provided by gmaxwell [https://people.xiph.org/~greg/openssl/] rather than the distribution package manager's library. (Warning: as of May 2014, these libraries are still vulnerable to the Heartbleed exploit, which affects Bitcoin through the RPC interface and payment protocol; it may also expose other applications on your system which use OpenSSL).

Revision as of 15:28, 1 August 2015

OpenSSL Without Elliptic Curve Support

Some algorithms in OpenSSL library may be restricted by patent law. Due to strong coupling between the elliptic curve support Bitcoin requires and these nominally non-free algorithms, some Linux distributions (most notably Fedora) ship OpenSSL libraries with elliptic curve support disabled. Since Bitcoin depends on elliptic curve cryptography (although not on any restricted algorithms), it cannot be used with such libraries.

Fixes / Workarounds

One workaround is to compile your own OpenSSL and use this rather than the distribution package manager's library.