A bad hard coded hash in tools/vars/wireguard.yml might cause the python Script to fail.

[Koladweep]

Describe the bug
Upon downloading wireguard-go-0.0.20250515.tar.xz, from https://git.zx2c4.com/wireguard-go/snapshot/wireguard-go-0.0.20250515.tar.xz, I found this to be true:
npd@mycomputer:~/windscribe-source$ sha256sum wireguard-go-0.0.20250515.tar.xz
5ee2043f56e24cb7256d8e53588eacad97e3f90256d5f85f74035106f1e7c1e7 wireguard-go-0.0.20250515.tar.xz

Which differs from the checksum embedded in the mentioned file tools/vars/wireguard.yml, i.e. 'c2861e387555fe8b93a123dc34a2e150971b831dda26dbac65a8db006654c859'

I assume this is due to load balancing or dynamic generation of the archive.

Suggested fix- choose a different download source.

OS and app information:

• OS: Debian Bookworm.
• App version Main branch, current as of 17/03/2026. latest release being v2.20.7

I noticed that the actual build files use a different source for wireguard from github.

[jaxu]

You are very correct. This was actually just a wrong hash.

We have already corrected this in our local repo but this change has not yet propagated to this public one. If you need to work with this you can just change the hash in wireguard.yml for now. This will be corrected once we push the 2.22 guinea pig releases here.

[Koladweep]

Thank you. Wishing the best for the coming release!