-
Notifications
You must be signed in to change notification settings - Fork 50
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
Remove openssl dependency - use Rustls for acme / letsencrypt #192
Comments
|
|
async-acme looks even better indeed! |
until this issue is solved, it might make sense to consider acme-micro which seems a (somewhat) more actively maintained fork of |
This issue just got a bit more important. My own CI pipeline broke because of openssl version mismatch. I didn't know that could happen. It even makes running the docker container impossible. |
Try on push Try develop #192 https setup docs try again add environments fix yml Try nested job try again Require secrets remote_host fix inputs Add remote host for production
I think (although I'm not entirely sure) that OpenSSL is the only runtime dependency of
atomic-server
. It's required only for the HTTPS setup process, which is currently done usingacme_lib
.I've had some issues with openssl as a dependency. It makes compiling harder, and i've had that binaries didn't run because of OpenSSL version mismatches. Not fun.
Options:
Fix current implementation
acme_lib
acme_lib works fine, but it has a bunch of dependencies on OpenSSL for crypto stuff. This could be fixed, with ring for example. But it's not easy - lots of PEM dependencies, which ring doesnt support (see issue in acme-lib)
rustls-acme
async-acme
acme-micro
Uses openssl, so no
instant_acme (my favorite atm)
(current implementation)
I made the
https
andhttps_init
optional features. Not a real solution!Custom implementation
Poem has a custom implementation
future-io-utils also
The text was updated successfully, but these errors were encountered: