checksum mismatch on 1.2.1 release

[timblaktu]

I wasn't able to install kauthproxy via krew because of a checksum mismatch error. I was able to reproduce the error outside of kubectl/krew:

[LAPTOP-9M95256K]/home/tim/tmp > ls -la kauthproxy_linux_amd64.zip*
-rw-r--r-- 1 tim tim 19432320 Dec  6 21:16 kauthproxy_linux_amd64.zip
-rw-r--r-- 1 tim tim       93 Dec  6 21:16 kauthproxy_linux_amd64.zip.sha256
[LAPTOP-9M95256K]/home/tim > cat kauthproxy_linux_amd64.zip.sha256
8199aad0e90d626bf37886558e2a13ae8b13ec280d47c7d52957addf2ce0c283 *kauthproxy_linux_amd64.zip
[LAPTOP-9M95256K]/home/tim > sha256sum kauthproxy_linux_amd64.zip.sha256
ae49e1c71a112af7a319547091ab7785ce7edd2804ada789fdafbb8106b430b7  kauthproxy_linux_amd64.zip.sha256

EDIT: I see my error in the sha256sum line above. See comment below. Checksum is matching fine outside of my work environment, where I can easily reproduce this:

~  >> mkdir tmp
~  >> cd tmp
~/tmp  >> wget https://github.com/int128/kauthproxy/releases/download/v1.2.1/kauthproxy_linux_amd64.zip
.
.
.
~/tmp  >> wget https://github.com/int128/kauthproxy/releases/download/v1.2.1/kauthproxy_linux_amd64.zip.sha256
.
.
.
~/tmp  >> ls -la
total 19008
drwxr-xr-x 1 tim tim      512 Apr 12 09:23 .
drwxr-xr-x 1 tim tim      512 Apr 12 09:22 ..
-rw-r--r-- 1 tim tim 19408014 Dec  6 21:16 kauthproxy_linux_amd64.zip
-rw-r--r-- 1 tim tim       93 Dec  6 21:16 kauthproxy_linux_amd64.zip.sha256
~/tmp  >> cat kauthproxy_linux_amd64.zip.sha256
8199aad0e90d626bf37886558e2a13ae8b13ec280d47c7d52957addf2ce0c283 *kauthproxy_linux_amd64.zip
~/tmp  >> sha256sum kauthproxy_linux_amd64.zip
04f544ac96e5f710d3d1cbbb60e6b35c22f6a3b0ab30924e815f6c48fd40a651  kauthproxy_linux_amd64.zip

[timblaktu]

I see my error in the sha256sum line, where I was taking the sha256sum of the sha file, not the .zip file. Correcting this in my home laptop WSL environment shows there's no issue there. The issue does however, persist on my work environments, so like this issue, I need to look into the firewall/proxy settings at work to see what could be manipulating downloads like this.