Consider switching from subprocess+openssl to Cryptography about acme-tiny HOT 6 CLOSED

I think I still want to keep this project as copy-paste friendly as possible, so I'd rather keep just openssl subprocess based.

from acme-tiny.

That's outside the scope of this project. Read https://github.com/diafygi/acme-tiny#feedbackcontributing, especially: This script must stay under 200 lines of code to ensure it can be easily audited by anyone who wants to run it.

Also, there is a huge number of ACME clients. Why do you insist on this one, which has a very specific goal, to change to something that is not its goal?

from acme-tiny.

Please read this: #237 (comment)

from acme-tiny.

OK. Possibly make an option? I mean refactor the code with a global switch that switches between Cryptography and openssl ? (and openssl cmd by default)

from acme-tiny.

Also, in 2020 installing a python library using Dockerfile is not that difficult. Fedora 31 has the package for your great library (I don't know, possibly earlier versions also have). Is any chance to consider Cryptography as a non-default stub for crypto functions?

from acme-tiny.

Because it's really tiny! :) and I like it.

from acme-tiny.