Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Unbundle OpenSSL #103

Open
mvanbaak opened this issue Nov 13, 2024 · 1 comment
Open

feat: Unbundle OpenSSL #103

mvanbaak opened this issue Nov 13, 2024 · 1 comment

Comments

@mvanbaak
Copy link

Description

At the moment Cargo.lock includes openssl-src-300.3.2+3.3.2 (a vendored copy of OpenSSL)
Instead of bundling this, use the OpenSSL that is installed on the machine the binary will run on.
Or at least make it a build option so this behaviour can be disabled and the system OpenSSL is used if this feature is not selected.

Additional Information

No response

@dan-online
Copy link
Owner

I'll look at maybe providing an unbundled version of the binaries, as for building, the default is to not bundle anything. The "vendored" feature can be provided, which is used for the docker/binaries as documented in https://github.com/dan-online/autopulse#setup

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants