I had no idea this issue had been identified. While I find this tool very useful, the project is seeming rather questionable to me now.
21 points
that’s what automation is for - nobody is going to manually check them, but anyone is able to automatically set something up to check their hashes in change… the fact that it’s possible that anyone is doing that now that it’s a known issue perhaps makes it less problematic as an attack vector
2 points
That is true, but also nobody is doing it. Just like nobody is verifying Signal’s “reproducible builds”.
4 points
are you sure?
there could be thousands just waiting for a failure to come out and say “HEY THIS IS DODGY”
1 point
*
