Solved Certbot stopped working due to cryptography>=3.2

[Aknot]

Hello,

Certbot doesn't work due to cryptography >= 3.2

pkg_resources.ContextualVersionConflict: (cryptography 2.9.2 (/usr/local/lib/python3.7/site-packages),
Requirement.parse('cryptography>=3.2'), {'PyOpenSSL'})

Need advise on how to continue, abondon certbot for acme.sh or wait?
Can you be sure that there will be an update for cryptography in the ports?

Thank you,

253730 – security/py-openssl: Revert back to 19.1.0

bugs.freebsd.org

 

[trev]

I've been happily using security/acme.sh for ages on three systems since it is simply a Bourne shell script and has no other dependencies. It doesn't even need to run as root. KISS in action.

 

[msplsh]

This seems ridiculous. Why not just use openssl from ports?

 

[SirDice]

Apparently this is only a problem on FreeBSD 11? Keep in mind that 11 will be EoL around September, so you may want to invest your time in preparing to upgrade to 12.2.

 

[Aknot]

I've been happily using security/acme.sh for ages on three systems since it is simply a Bourne shell script and has no other dependencies. It doesn't even need to run as root. KISS in action.

Might need to consider acme.sh instead ?

 

[Aknot]

This seems ridiculous. Why not just use openssl from ports?

Beats me.

 

[Aknot]

Apparently this is only a problem on FreeBSD 11? Keep in mind that 11 will be EoL around September, so you may want to invest your time in preparing to upgrade to 12.2.

But I'm already on:

root@srv05:/usr/home/me # uname -a
FreeBSD srv05 12.2-RELEASE-p4 FreeBSD 12.2-RELEASE-p4 GENERIC  amd64

 

[diizzy]

The issue is that we have are very conservative regarding bumping python ports because of breakage but as an effect of it we lag quite a bit behind upstream in some areas.

245930 – security/py-openssl: Update to 19.1.0

bugs.freebsd.org

The current "workaround" is to use lego (based on go), acme.sh or uacme .
I've had great success using lego personally...

 

[Aknot]

The issue is that we have are very conservative regarding bumping python ports because of breakage but as an effect of it we lag quite a bit behind upstream in some areas.

245930 – security/py-openssl: Update to 19.1.0

bugs.freebsd.org

The current "workaround" is to use lego (based on go), acme.sh or uacme .
I've had great success using lego personally...

Just tried security/acme.sh and one of our sites is already up and running

 

[Aknot]

I've been happily using security/acme.sh for ages on three systems since it is simply a Bourne shell script and has no other dependencies. It doesn't even need to run as root. KISS in action.

Now installed and running ?

 

[Aknot]

Solved, new version of security/py-cryptography added => https://svnweb.freebsd.org/ports?view=revision&revision=566534

 

[GreenReaper]

It wasn't solved for me (even though I was on 11.4, supposedly, in a jail), so I commented out the block in the Makefile starting:

# We need to keep old py-cryptography and py-openssl for 11.x release

...did a make reinstall, and certbot started working again. Just in case anyone else runs into that issue.
We're planning to migrate these services to another system, but for now we need it working where it is.