[–] 32 points 1 year ago (6 children)

I assume this is because, in addition to the missing ciphers as referenced in the linked article, OpenVPN, even though it uses TLS, it initially uses a very identifiable handshake before initiating TLS, which is not hard to block. I have personally had problems specifically with OpenVPN being targeted/blocked in this way.

  • source
  • [–] 4 points 1 year ago* (1 child)

    Verify our no-logging policy through code inspection

    Couldn't a network appliance, iptables or a bpf program still be logging and we'd have no idea?

    Validate that the code running on our servers matches this public repository

    Yes but AFAIK it can't validate that the code you verified against is the same code actually powering your VPN session right now (could be a dummy box just used for validation), or that some other external hardware or superuser-level code isn't also listening in. Someone please correct me if I'm wrong.

  • source
  • [–] 1 point 1 year ago (1 child)

    Canada and the United States have banned or shut down torrenting sites, while Trinidad and Tobago imposes lengthy prison sentences for illicit media streaming.

    I assume this is what they're referring to, although you didn't specify your country. Seems accurate to me.

  • source
  • parent
  • context
  • [–] 3 points 1 year ago* (1 child)

    Sounds like an attempt to curb their massive abuse problem.

    On Matrix, you can actually upload files using special message types that don't even show up on normal clients, but persist forever... you can imagine the very illegal types of content that people post using such methods.

  • source
  • [–] 4 points 1 year ago*

    Basically instead of launching completely new processes for each tab, which uses the (now updated/different) binary on disk, it uses a small secondary process that stays running the whole time the browser is open, and new processes are forked from that one, which makes them all use the same in-memory copy of the old process even after the program is updated.

    This only works on *nix because you can't overwrite binaries on Windows that are in use... but Linux keeps the old binary in memory the whole time, so it doesn't care if you replace it, as it won't be used until you restart the program.

    So it doesn't actually update anything at all while it's running.

  • source
  • parent
  • context
  • view more: ‹ prev next ›