Wednesday, February 02, 2022

Re: SSL write error: certificate verification failed: certificate has expired

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEE7sBxPmxNSLEwQp4k5k1h0mWW9oAFAmH7gesACgkQ5k1h0mWW
9oBiBgf/fDMVK8mR3hpe3TwFanUp5KVEgb41y9oa3DagYn5mAL6MpS9K55Ctd8wC
kzDeuO+Wd7uhMLsKysLJC8pWUddBRL4wVjESDvyfZN6AovIMQNeQSOJ17+v+YUKI
6Oq5sqFv7kJ3pDBA16YpS4s2piRdb3lL7XSB/MVpnWcnhp/Zr46cSnMs2xq9x9YU
sHE09emdvOl8WCwG5MI0H5oQOCzRPu0Yzr7A+NuLB9W5OaYZdTjNF/FFSlgvUfnX
wCWtBq1mebH4AGuAfxb3qBBiUNuxkvMlDnvySCuok+iO8nnuw+QbnMVzv1Y3gocH
GhsLf63yht6zolsbSEns3mZMppxpBw==
=gPok
-----END PGP SIGNATURE-----
> 3. feb. 2022 kl. 08:01 skrev Yogendra Kumar Chaudhary <yogi9088@gmail.com>:
>
> Thanks for this information.
> I found on my machine that cert.pm expired on 30 May 2020. I can not switch
> to the new o OpenBSD version immediately due to other technical
> dependencies. Can you please suggest what should I do to resolve this issue?

If upgrading to a supported version is not an option, what's the rush in installing a new package?

Then again, since the error seems to be appearing during file retrieval, you could try to download the package file or files manually and see if you can install the package from the downloaded file. It is likely that you will need to resolve dependencies by hand, but your mileage will vary.

The other option would be to build the package from a local copy of the ports tree.

Both of those options are likely to be more work than doing incremental upgrades (which get even easier once you reach 6.6 which has sysupgrade(8)), or as already suggested, re-install with the most recent supported version and introduce the config and packages you know you need.

What fits your budget time- or money-wise is of course up to you.

All the best,
Peter


Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.

No comments:

Post a Comment