You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
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.
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 always1.22.5-devel-cf
. I tried to setGOROOT_BOOTSTRAP
to a valid Go working tree (version1.23.0
), but this didn't resolve the issue.Is there a way to work around this?
The text was updated successfully, but these errors were encountered: