-
Notifications
You must be signed in to change notification settings - Fork 30
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
Deprecation warning when signing/verifying JWKRSA objects #13
Comments
Thanks for opening an issue. We'd take a well written PR to use the other APIs. |
(It looks like the warning is emitted only when the certificate needs to be renewed, which makes this not as annoying as it would be if it were emitted on every run.) |
Why was this closed? certbot issues this warning now with every cert request. |
Because the issue was fixed in the josepy release over 4 months ago. How did you install Certbot? |
Sorry, yes, I just noticed that I can follow that link and see it was merged in April. I'm getting certbot from the official repo, wait a minute. It says it's version 0.26.1. There's no newer one if I try to upgrade. |
From our Ubuntu PPA? It looks like the maintainers haven't packed a version of @NCommander, do you have the cycles to do this? It should be very simple as very little has changed since the previous version and it is packaged on Debian. |
Yes, I updated my last reply twice. |
I'll take a crack at it tonight
…On Wed, Aug 15, 2018, 13:52 bolera ***@***.***> wrote:
Yes, I updated my last reply twice.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#13 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AALDQOpfnMPUQes0bO_elR7qj0kQgsHfks5uRIoggaJpZM4S2sey>
.
|
The renewal works, but this warning is sent into STDERR. |
Any news on this? I (re)installed certbot yesterday and keep getting this warning... |
@hlieberman, the most recent comment is relevant to you and can be fixed by updating the version of EDIT: It looks like the comment I was referring to was deleted, but a |
Still having the same issue after installing from |
I also installed via stretch-backports, as advised by your website, after having to re-install because of https ACME disabling. |
This should be fixed with the latest upload of certbot to stretch-backports.
In any regard, it's simply a warning, and shouldn't mess with anything.
(Albeit, being annoying).
…--
Harlan Lieberman-Berg
~hlieberman
|
Not sure, if I should open a new ticket, but as it got already mentioned above: the Ubuntu ppa hasn't been updated yet. It's still on certbot 0.26.1 and josepy is still 1.0.1, uploaded in February. Would be nice to get new packages at least with major version jumps. Thanks! |
/usr/local/lib/python2.7/dist-packages/josepy-1.0.1-py2.7.egg/josepy/jwa.py:107: CryptographyDeprecationWarning: signer and verifier have been deprecated. Please use sign and verify instead. It's still there. With a clean debian 9, as far as python and certbot go. |
@jult, that file path shows josepy 1.0.1 is being used. josepy 1.1.0 where this change is fixed is available in Debian 9. See https://packages.debian.org/stretch/python-josepy. EDIT: It's also in |
@bmw Yes, I fixed it doing
Strange how I got there without recalling a pip install. |
Added If possible, Certbot uses built-in support for OCSP from recent cryptography versions instead of the OpenSSL binary: as a consequence Certbot does not need the OpenSSL binary to be installed anymore if cryptography>=2.5 is installed. Changed Certbot and its acme module now depend on josepy>=1.1.0 to avoid printing the warnings described at certbot/josepy#13. Apache plugin now respects CERTBOT_DOCS environment variable when adding command line defaults. The running of manual plugin hooks is now always included in Certbot's log output. Tests execution for certbot, certbot-apache and certbot-nginx packages now relies on pytest. An ACME CA server may return a "Retry-After" HTTP header on authorization polling, as specified in the ACME protocol, to indicate when the next polling should occur. Certbot now reads this header if set and respect its value. The acme module avoids sending the keyAuthorization field in the JWS payload when responding to a challenge as the field is not included in the current ACME protocol. To ease the migration path for ACME CA servers, Certbot and its acme module will first try the request without the keyAuthorization field but will temporarily retry the request with the field included if a malformed error is received. This fallback will be removed in version 0.34.0.
The cryptography extension has deprecated [1] (since 2.0 - 2017-07-17) the
signer
andverifiier
methods, which results in this warning:Code I used to get this warning:
Environment:
[1] pyca/cryptography#3659
The text was updated successfully, but these errors were encountered: