@eff if i may invoke idris elba as stringer bell: "is you taking notes on a criminal conspiracy?"
which is to say: ARE YOU SERIOUSLY PUTTING YOUR RELEASES OF STINGRAY SOFTWARE ON MICROSOFT FUCKING SERVERS?
@eff @cooperq i do respect the use of zip archives on https://github.com/EFForg/rayhunter/releases for the resistance to length extension but it is fundamentally unserious to be telling people explicitly to go to a protest after making a specific fingerprintable connection to a microsoft web site
(yes it's the same thread as bluesky. i'm trying to embarrass your employer. apologies the harsh tone)
@eff @cooperq this page could be a great teaching opportunity about trust boundaries https://efforg.github.io/rayhunter/installation.html unfortunately you have to deal with cargo who (ed page, previously steve klabnik) refuses outright any way to make build scripts better or safer so it's still a toss up
i applied to NGI for a grant to work on literally this problem for cargo btw https://circumstances.run/@hipsterelectron/114610077000401178 if there is infrastructure work to do i can do it and make it reliable
@eff @cooperq just find it to be kind of fucked up to have a "legal disclaimer" in the readme while your download urls are owned and controlled by the largest surveillance contractor in the world. giving them your download numbers alone is a massive risk
i also find it extremely strange to provide sha256 checksums alongside each file instead of signatures since the checksums don't offer any additional guarantees except against data corruption. maybe that's an automatic thing microsoft does. i would definitely recommend signatures (rpgp is well done and the author is wonderful)
...but that's a nitpick and does not put users in a direct line to be tracked during protests while executing your code