• mirshafie@europe.pub
    2·
    3 hours ago

    It was annoying as hell trying to download a LaTeX compiler and having the entire word be blocked, presumably because certain degenerates use latex - the material - for immoral acts.

        • fishos@lemmy.worldEnglish
          45·
          2 hours ago

          So the solution to “I use a bad app” is comment spam?

          And why not repost the OP image? They went and took their own screenshot of the tweet. Why take your own? What if they’d edited it? I know it’s nothing here, but it feels shady. It’s karma whoring at best, and malicious at worst. We shouldn’t normalize this.

            • fishos@lemmy.worldEnglish
              25·
              2 hours ago

              It’s not. See, don’t have to click a thing. It’s just there. Sorry you use an inferior app. That’s your problem tho. So could you stop spamming the comments? Or get an app that doesn’t handicap you and make it others problem? Kthnxbai!

              Here’s even the actual OP screenshot that you “can’t see”. Funny how it’s just an image I can save to my phone but somehow you have to “access twitter” and then post your own version of.

              Get a better app or stop lying.

  • [object Object]@sh.itjust.worksEnglish
    32·
    21 hours ago

    My original guess was that they’re intercepting DNS, but since boobs is in the path, it wouldn’t be sent. How does this work?

    • Brkdncr@lemmy.world
      12·
      17 hours ago

      It’s either

      • Client side ssl forward proxy (MitM cert installed on client)
      • in-line decryption in the server
      • client side software
      • tls downgrade
      • cert authority compromise
    • baltakatei@sopuli.xyz
      8·
      17 hours ago

      Right? If it were an unencrypted HTTP GET request, then every router on the way would see the plaintext string boobs in the URL and therefore intercept it.

      If I had to guess, Iran has so few landline connections that they man-in-the-middle every TLS connection they can by either forcing every server to hand over their private key files (difficult) or by forcing a certificate authority trusted by default Web browsers (there’s a lot of them) to issue certificates for every top level domain they see in SNI data attached to encrypted packet headers; the latter method need not even require participation by Iranian servers, so long as the traffic is bottlenecked for man-in-the-middle attacks and outsiders don’t question unusual certificate authorities being used.

    • bcovertigo@lemmy.worldEnglish
      19·
      21 hours ago

      They are giving response codes like 403 so it’s not a failure to resolve and I agree it’s not DNS… It’s behaving differently based on different sub pages so it’s something underneath the https encryption. Maybe an intermediary WAF that decrypts? Maybe some weird server side tooling that has govt provided?

      I would guess WAF but I’d love to hear from someone who actually knows.

    • Sundray@lemmus.orgOPEnglish
      401·
      20 hours ago

      Presumably because instead of responding to the request for boobs.jpg with with an HTTP 404 error (meaning, “not found”), Iran’s censorship tech returns a 403 error (meaning basically "you are forbidden from accessing this resource).

      The “boobs” are “forbidden” you see; the tech mirrors the ruling party’s moral stance, probably coincidentally. Trying the same curl command in Russia and China will likely just get you a 404 error, so the joke really only works with Iranian servers. The 404 version is slightly less funny: “We couldn’t find the boobs!”