Date: Sat, 20 Apr 2024 14:29:01 -0700 From: paul beard <paulbeard@gmail.com> To: FreeBSD Questions List <questions@freebsd.org> Subject: Re: certbot Message-ID: <CAMtcK2pTKSHpOCKhEdWSvLyT1fBvjm50zZ8LhF-jbDjmFzBJGA@mail.gmail.com> In-Reply-To: <20240420153432.671268909CE2@ary.qy> References: <20240420091633.00002f24@seibercom.net> <20240420153432.671268909CE2@ary.qy>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] The meta question for me and perhaps others running FreeBSD 13 is what changed and how do we prepare for it if we expect to run certbot in FreeBSD 14? I run it as I always have, since release 11 or so. 00 00 * * Sun python -c 'import random; import time; time.sleep(random.random() * 3600)' && /usr/local/bin/certbot renew --renew-hook 'service nginx reload' Will I need to change that? Do the folks at EFF know/have they documented what changed and how to manage it? On Sat, Apr 20, 2024 at 8:35 AM John Levine <johnl@iecc.com> wrote: > It appears that Gerard E. Seibert <jerry@seibercom.net, > questions@freebsd.org> said: > >If I run the command from the command line, it works as expected. I did > >place the following in the environment: CRYPTOGRAPHY_OPENSSL_NO_LEGACY=1 > > >I still do not understand why this error only happens from CRON. > > Most likely because that variable is not there. Cron uses a standard > rather sparse environment. See "man 5 crontab". > > In this case rather than messing with the script, just set the > variable on the command line in the crontab, e.g. > > 0 1 * * * CRYPTOGRAPHY_OPENSSL_NO_LEGACY=1 certbot ... > > R's, > John > > > -- Paul Beard / www.paulbeard.org/ [-- Attachment #2 --] <div dir="ltr">The meta question for me and perhaps others running FreeBSD 13 is what changed and how do we prepare for it if we expect to run certbot in FreeBSD 14? I run it as I always have, since release 11 or so. <div><br></div><div><font face="monospace">00 00 * * Sun python -c 'import random; import time; time.sleep(random.random() * 3600)' && /usr/local/bin/certbot renew --renew-hook 'service nginx reload'</font><br></div><div><font face="monospace"><br></font></div><div><font face="arial, sans-serif">Will I need to change that? Do the folks at EFF know/have they documented what changed and how to manage it? </font></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Apr 20, 2024 at 8:35 AM John Levine <<a href="mailto:johnl@iecc.com">johnl@iecc.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">It appears that Gerard E. Seibert <<a href="mailto:jerry@seibercom.net" target="_blank">jerry@seibercom.net</a>, <a href="mailto:questions@freebsd.org" target="_blank">questions@freebsd.org</a>> said:<br> >If I run the command from the command line, it works as expected. I did<br> >place the following in the environment: CRYPTOGRAPHY_OPENSSL_NO_LEGACY=1<br> <br> >I still do not understand why this error only happens from CRON.<br> <br> Most likely because that variable is not there. Cron uses a standard<br> rather sparse environment. See "man 5 crontab".<br> <br> In this case rather than messing with the script, just set the<br> variable on the command line in the crontab, e.g.<br> <br> 0 1 * * * CRYPTOGRAPHY_OPENSSL_NO_LEGACY=1 certbot ...<br> <br> R's,<br> John<br> <br> <br> </blockquote></div><br clear="all"><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature">Paul Beard / <a href="http://www.paulbeard.org/" target="_blank">www.paulbeard.org/</a><br></div>home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAMtcK2pTKSHpOCKhEdWSvLyT1fBvjm50zZ8LhF-jbDjmFzBJGA>