From: John Covici <covici@ccs.covici.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] problem with certbot -q renew
Date: Thu, 31 Oct 2024 09:18:40 -0400 [thread overview]
Message-ID: <31C8195D-19E9-4FE5-8ECC-7EC9EEF71532@ccs.covici.com> (raw)
In-Reply-To: <2215517.Icojqenx9y@rogueboard>
> On Oct 31, 2024, at 5:59 AM, Michael <confabulate@kintzios.com> wrote:
>
> On Thursday 31 October 2024 05:40:32 GMT John Covici wrote:
>> Hi. So, I have a certificate from lets encrypt and since the last update
>> whenever I run certbot -q renew I get the following:
>>
>> /usr/lib/python3.12/site-packages/certbot/ocsp.py:238:
>> CryptographyDeprecationWarning: Properties that return a naïve datetime
>> object have been deprecated. Please switch to this_update_utc. if not
>> response_ocsp.this_update:
>> /usr/lib/python3.12/site-packages/certbot/ocsp.py:240:
>> CryptographyDeprecationWarning: Properties that return a naïve datetime
>> object have been deprecated. Please switch to this_update_utc. if
>> response_ocsp.this_update > now + timedelta(minutes=5):
>> /usr/lib/python3.12/site-packages/certbot/ocsp.py:242:
>> CryptographyDeprecationWarning: Properties that return a naïve datetime
>> object have been deprecated. Please switch to next_update_utc. if
>> response_ocsp.next_update and response_ocsp.next_update < now -
>> timedelta(minutes=5): Is this a harmless warning, or do I need to do
>> something?
>>
>> Thanks in advance for any suggestions.
>
> Take a look here:
>
> https://github.com/certbot/certbot/issues/9967
>
> You could use 'export PYTHONWARNINGS=ignore' as a workaround until the certbot
> devs address this issue.
OK, thanks — I will do that.
prev parent reply other threads:[~2024-10-31 13:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 5:40 [gentoo-user] problem with certbot -q renew John Covici
2024-10-31 9:59 ` Michael
2024-10-31 13:18 ` John Covici [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=31C8195D-19E9-4FE5-8ECC-7EC9EEF71532@ccs.covici.com \
--to=covici@ccs.covici.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox