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.
0 Boosts
0 Likes
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
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