On 12/06/16 13:20, Neeraj Sharma wrote:
It's good to provide openssl as an alternative. That said, it would be nice
if it actually were an actual alternative instead of "one works with some
but not others". So, I'd appreciate some sort of [quick] analysis/writeup
on why libressl wouldn't work with Erlang, along with reporting the findings
to the right upstream community.
I agree. That would be the right thing to do, but it'll be a lot more
work than what I can do right now. Parking it for future.
Additionally, I have a build working with openssl v1.0.1j with a
typical configuration which I've had past experience with. Is there
any specific version anyone prefers? Although I can submit the
existing work for starters and then plan any update what so ever.
Well, either you know why libressl won't work with Erlang, or you don't
have a problem. Someone who was once reading a draft of mine gave me a
valuable tip: "if you have evidence, present it. otherwise, shut up".
I'll assume 1.0.1j is some sort of typo. The only acceptable version of
openssl ever is the very latest stable (cf. original motivation for
moving it into packages).
Assuming there indeed is a problem with libressl & Erlang, and you have
the openssl build figured out, seems like the best option is to add
openssl and remove libressl.
That said, openssl needs to be reasonably easy to update, given that it
needs to be updated often.
