Packages for RPM and DEB about aws-lc HOT 4 CLOSED

Hi, thanks for the feedback and interest in AWS-LC. I see your initial concern with ACCP's use in corretto/amazon-corretto-crypto-provider#269 has been resolved (ACCP bundles AWS-LC for it's customers).

We've looked into adding support for Amazon Linux (internal references: CryptoAlg-792 and /CryptoAlg-1069) but not other distributions. What is the best way to let customers consume AWS-LC? If we install AWS-LC as libcrypto.so to /lib/x86_64-linux-gnu/ (for Ubuntu) we will conflict with other libcrypto.so's (e.g. OpenSSL). If we install with a different name or in a subfolder it is harder to consume AWS-LC because other libraries to update their build to find/handle the different path. Which of these did you have in mind? Do you have another idea that would make it easy to consume AWS-LC?

Looking at Ubuntu 22.04:

• libssl-dev (OpenSSL) -> /usr/lib/x86_64-linux-gnu/libcrypto.so
• libwolfssl-dev -> /usr/lib/x86_64-linux-gnu/libwolfssl.so
• BoringSSL -> I can't find this
• android-libboringssl -> /usr/lib/x86_64-linux-gnu/android/libcrypto.so.0

W are focusing on making it easier to consume AWS-LC through other higher level libraries that do the bundling for us (e.g. ACCP).

from aws-lc.

This issue has not received a response in 1 week. If you want to keep this issue open, please just leave a comment below and auto-close will be canceled.

from aws-lc.

This issue has not received a response in 1 week. If you want to keep this issue open, please just leave a comment below and auto-close will be canceled.

Closing issues does not resolve them. I recommend against bots like these since you'll just end up with worse issue tracking and duplicates.

On topic, yes, my primary problem has been resolved and I've helped clarifying the documentation.

As for helping customers use it; It's a chicken-and-egg problem, because you can't just drop-in-and-replace an existing implementation. This is a known problem with GnuTLS and BoringSSL as well. You do have one benefit over these two though, since you already have one application(-library) that uses it.

For now, I think the best cause of action, would be to create a Debian Sid and Fedora Linux package downstream. If you have the resources to maintain these, future version of AWS-LC can use the native package of CentOS or Ubuntu in the future.

from aws-lc.

Hey @KevinAtSesam

RPM and/or DEB packages are potential distribution mechanisms that we are considering for easing the integration story for developers looking to use AWS-LC. At this time though we don't have anything more specific that we can share in terms of timelines or a public roadmap, but we are tracking such an ask within our internal process planning.

I am going to move to close this issue, as we prefer to keep our set of open GitHub issues limited to bug reports and feature request that we are looking to implement in the near term (or are open to outside contributions). We appreciate you taking the time to open this feature request and to share with us your input and general use cases for such a feature.

from aws-lc.