OpenSSL 1.0 / 1.1 Compatibility

[internetarchive]

OpenSSL 1.0 / 1.1 Compatibility

[bnewbold]

I poked at this a bit today. It looks like the community (or at least the rust-server upstream, mostly maintained by Metaswitch) has moved to the OpenAPITools/openapi-generator codegen project (away from swagger-api/swagger-codegen). There has been recent/continuous progress on the hyper server bindings there.

However, switching currently wouldn't actually fix this OpenSSL dependency issue, because current the swagger-rs crate is also still locked in to the old dependency; the relevant tracking issue is: Metaswitch/swagger-rs#66

Looks like there is a path forward using hyper-openssl, but we should wait until that lands in a stable openapi-generator release.

@miku mentioned he ran in to this issue on Arch linux and I wonder if there is an "easy" build workaround using OPENSSL_LIB_DIR on that platform as well.

[bnewbold]

This has been mitigated for now by removing HTTPS support from the fatcat-openapi crate as used by fatcat.

This is a short-term solution and a hack. It also breaks using fatcat-openapi as a client library in any form. In the medium-term future we will need to fix this dependency tangle so we can switch to the modern openapi code generation pipeline.

This workaround became a priority because my debian laptop could no longer build the project after I upgrade to buster.

[bnewbold]

Closing this issue because the specific problem is resolved. Upgrading code generation is a separate task.