Closed ymatsiuk closed 3 weeks ago
Yeah, this was somewhat fixed in 2.0.0-beta2 with a new 10 year cert. There's limited good options since I'm too lazy to write the code to generate the cert/key in Go. I don't want to add external dependencies to the tests, hence not making generating the cert on the fly via make test
and I also want to enable people running tests via go test
.
If it really bothers you, I'd accept a PR to do it in pure Go as part of go test
if you feel strongly about the 100 year thing.
if you feel strongly about the 100 year thing
Haha, not at all. I'll switch to beta for now. Thanks :+1:
Would love feedback on the beta... there are some big and likely somewhat controversial changes. Squeaky wheel will get the grease!
Describe the bug: Manually building
v1.17.0
fails due to expired certificateTo Reproduce:
Expected behavior: It should always build, even in a 100 years from now the code should just build and tests succeed :wink:
Additional context: NixOS builds binaries from the source by fetching the code from the repository. Most of the time it's enough to build something once and cache it, but sometimes dependencies change triggering massive rebuilds. This has started to fail now due to expired certificate:
To be frank it seems like an interesting challenge to solve, and in general interesting perspective to put own software into. Will my software build in a hundred years from now? :wink: First thing that comes to my mind is to generate these certs on the fly in the test, WDYT?