-
Notifications
You must be signed in to change notification settings - Fork 141
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
FreeBSD11: LetsEncrypt certificate update #266
Comments
FreeBSD 12 works. So maybe you can simply copy some files from that. |
Hi @ole-tange ... actually, the Of course you can always tweak your repo config and force it to use HTTP. I hate this solution personally, which is why I only get the 2-3 packages needed to rebuild the CA file over HTTP, compare them to static hash values, then rebuild the CA file so the reset of the install can download packages over HTTPS. But I'm a little more paranoid than most. In theory HTTP should be safe, since FreeBSD still uses signatures on the package files to verify the download. So all you're leaking to an observer is the list of packages you're installing (and from where), which most people don't consider sensitive. |
I updated to 4.2.14. The problem is still there. When would you say I should retry updating? In a week? |
@ole-tange the Windows/MacOS systems are both tied up on another project, so I'm waiting for them to finish. Hopefully by the end of the week, which would mean mid to late next week, assuming there aren't too many broken builds I need to investigate/resolve. In the interim, I'm curious whether running the It should be safe to run that script as root |
Running:
gives:
This is apparently due to a LetsEncrypt certificate that expired.
I do not know how to fix this, so I have asked on StackExchange for a solution to this:
https://unix.stackexchange.com/questions/737022/freebsd11-certificate-verification-failed
The text was updated successfully, but these errors were encountered: