go icon indicating copy to clipboard operation
go copied to clipboard

Unable to upgrade the go version

Open lakshya-chopra opened this issue 1 year ago • 5 comments

Hello,

I'm trying to integrate PQ-TLS into an application that requires Golang version 1.23.0 or higher due to certain dependencies. However, during the build process of this modified golang, the version I end up with is always 1.22.5-devel-cf. I tried to set GOROOT_BOOTSTRAP to a valid Go working tree (version 1.23.0), but this didn't resolve the issue. Is there a way to work around this?

lakshya-chopra avatar Oct 22 '24 07:10 lakshya-chopra

At the moment this fork is based on Go 1.22. We plan to rebase on 1.24 when that comes out. (The reason we skip 1.23 is that it comes with its own partial Encrypted ClientHello implementation.) Upstream Go 1.23 support X25519Kyber768 btw by default.

bwesterb avatar Oct 22 '24 10:10 bwesterb

Hello @bwesterb , While it's true that the upstream go 1.23 does support X25519Kyber768, it doesn't support Post Quantum Signature algorithms unlike this fork. However, I did find a workaround for this (which obviously is not very practical & just a temporary solution) - I copied the src/crypto & src/vendor/ directories from this fork to a standard go 1.23 release & apparently it did work. Now I'm not sure whether it would pass all the test cases, but since our use-case is still in development, it allows us to do some initial testing of the project.

Thank you for your efforts.

lakshya-chopra avatar Oct 22 '24 18:10 lakshya-chopra

Hello, with the release of Go 1.24, Go 1.22 is now EOL, and has been removed from Nixpkgs, which means we can't use cloudflared anymore. Would it be possible to rebase on 1.24 as mentioned?

uku3lig avatar Apr 02 '25 20:04 uku3lig

We're working on it, but it's quite a big lift.

bwesterb avatar Apr 03 '25 07:04 bwesterb

Any chance we could get a quick update on when a version bump might happen? Thanks for the awesome work!

haritzsaiz avatar Dec 16 '25 11:12 haritzsaiz