Notice: Chromium Code Search is currently experiencing intermittent issues. Some pages may load slowly or fail to load. We are actively working on a fix.
i found that firefox had started using http:// in the URL bar after my entire lifetime experience with firefox defaulting to https:// and SCREAMING at me for any site without a TLS certificate. so i tried looking into the EFF's HTTPS Everywhere extension, thinking it could circumvent this unannounced policy decision
i will say one thing that struck me. the author of this build script is clearly extremely well-trained in the quoting semantics of the shell https://github.com/EFForg/https-everywhere/blob/master/make.sh
i did think they began to fly just a little too close to the sun when they started writing cryptographic key material to static paths in /tmp/. sir this is a wendy's
i also have to admit that it's a pretty funny gag how none of the three separate ways indicated to avoid the damn thing "updating" behind your back actually stop it from updating and one of them instead adds 127.0.0.1 as an update URL. brilliant comedy
so this demonstrates an instructive microcosm of two separate phenomena:
(1) organizations who adore LLM slop but cosplay a controlled resistance are nearly always directly working for intelligence agencies on blatant cryptographic backdoors
(2) tech-flavored libertarian legal types who suddenly came out of the woodwork after the black panthers were killed or imprisoned and wouldn't fucking shut up about "code is law" and "freeze peach" really, really don't like making strong cryptographic contracts that secure free speech on the internet with anonymity, decentralization, and of course actual encryption
the end is closing in on our dear friend richard stallman, and his legal compatriate larry lessig, who of course comes from harvard
it turns out that the code for downloading missing
verified_contents.jsonfiles from the webstore had two longstanding bugs that we never noticed due to insufficient tests:a) Returning the results of a boolean expression as an integer
b) Use after free of an object
@hipsterelectron oh no!
what could possibly be causing that??
oh https://chromium.googlesource.com/chromium/src.git/+/e4de9f973eae513486d2912e1793e943fce70014%5E%21/#F9