otolonetworks / otp-osv Goto Github PK

When compiling a custom OSv image (from recent master on their repo), I seem to need a 1.0.x series to be compatible with this repo. (Ultimately at runtime it seems to check for the SSLeay symbol which is no longer exported in OpenSSL 1.1. I'm doing some extra hoops with the included crypto.so here to even be able to find a libcrypto.so.1.0.0 since that's what my system calls it.)

Does that seem correct? What version of OpenSSL / osv are you using when you build these OTP libraries?

I'm interested in using the rebar3_osv plugin, and this fork is required. I'm wondering about reviewing the patches, and if they might eventually be accepted by upstream?

Ideally the patches could be isolated into small + atomic git commits on top of the vanilla OTP sources.

As well, in general I'm wondering about how this repo and the patches would be maintained over time? (not expecting any sort of commitment, just wondering about the future)