Bug 1023017 - Restore ECC support in Erlang's crypto library
Restore ECC support in Erlang's crypto library
Product: Fedora
Classification: Fedora
Component: erlang (Show other bugs)
Unspecified Unspecified
unspecified Severity high
: ---
: ---
Assigned To: Peter Lemenkov
Fedora Extras Quality Assurance
Depends On:
Blocks: ecc 1086146
  Show dependency treegraph
Reported: 2013-10-24 09:03 EDT by Peter Lemenkov
Modified: 2014-08-27 14:57 EDT (History)
8 users (show)

See Also:
Fixed In Version: erlang-17.2.1-1.fc21
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2014-08-27 14:57:51 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Peter Lemenkov 2013-10-24 09:03:12 EDT
Right now ECC is disabled explicitly since it looks like Erlang's crypto library assumes that it's either available fully or not. We've just enabled few ECC curves so this confuses erlang-crypto and leads to a startup issue like this:

=ERROR REPORT==== 24-Oct-2013::16:30:48 ===
Unable to load crypto library. Failed with error:
"load_failed, Failed to load NIF library: '/usr/lib64/erlang/lib/crypto-3.1/priv/lib/crypto.so: undefined symbol: EC_GROUP_new_curve_GF2m'"
OpenSSL might not be installed on this system.

We should patch crypto module to provide available ECC bits instead of disabling it completely.
Comment 1 Travis Paul 2013-11-17 22:19:32 EST
I was seeing the startup errors you mentioned above and I seemed to have resolved them by installing the openssl-libs package. Would it be possible to add openssl-libs as an erlang-crypto requirement until the patching you mention is complete?
Comment 2 Konrad Gądek 2013-12-13 10:50:58 EST
What's the status of this one?
Comment 3 Peter Lemenkov 2013-12-27 04:41:22 EST
(In reply to Konrad Gądek from comment #2)
> What's the status of this one?

Hello All!
Despite of Christmas and the rest of the Holidays we're working on it - stay tuned!
Comment 4 Eiichi Tsukata 2014-01-16 07:19:16 EST
It seems that the following commit fix the problem:

It will be merged to the otp upstream soon.

Note You need to log in before you can comment on or make changes to this bug.