JakeDern commented on issue #413: URL: https://github.com/apache/arrow-rs-object-store/issues/413#issuecomment-3156537858
@tustvold Unfortunately it seems aws-lc-rs is not approved for me to use at my current company either. I'm willing to do the work to add multiple crypto providers including aws-lc-rs and open-ssl if that's acceptable. I think it could be done via mutually exclusive features or by some runtime configuration that allows setting the provider. The downside of the former being the usual pitfalls of mutually exclusive features, the downside of the latter being most people will only use one provider and so will have extra deps for the default + 1 if they enable an optional provider. A third options, is we could also make all crypto providers opt-in and force every user to add at least one feature to choose one, but that's a breaking change and also a usability burden. Let me know what you think, again I'm happy to take this up, but the approaches are quite different so I'd like some direction before starting. I personally think keeping the default crypto provider as-is and having features to add more providers + a runtime option to change the provider is the best middle-ground. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: github-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
