In <list-11360473@2rosenthals.com>, on 12/12/24
at 03:00 PM, "Peter Moylan" <ecs-isp@2rosenthals.com> said:
Hi Peter,
>At last! Apparently my account key was out of date, so I had to go back
>to "uacme -v new",
I've not seen anything resemblng and out of date failure from Let's
Encrypt. The account private key is typical x509 private key. It's got
not timestamp info. You can display it with openssl's x509 command.
You did mention that when you ran uacme new with the mismatched DLLs, you
got an error messsage when uacme completed. Perhaps the account creation
failed and we did not realize it?
>busy, as someone mentioned recently) I got my certificate. Now I just
>have to set up scheduling to get a new certificate after 80 days.
>but I didn't manage to find out what package
>CURL4.DLL is in.
The package names are pretty consistent. A the package name for a package
that contains only DLLs is going to be prefixed with lib. So it's libcurl
in this case. The full package name is suffixed with a version and a
platform and an epoch, but these will default so you rarely need to
provide them.
yum whatprovides curl4.dll
will find the package name is libcurl-7.75.0-2.oc00.pentium4 which means
the rpm file name is libcurl-7.75.0-2.oc00.pentium4.rpm.
>I got a checksum error on
>one package, but apparently that wasn't vital.
The spurious checksum report is a known issue. It's documented in
ArcaNoae wiki, somewhere.
tilbake listen