PIA Chrome extension

my country blocked all protocols offered by PIA but Chrome extension stile work and That's what worries me

Maybe PIA Chrome extension broken or dns leak from Chrome extension and not give enough security so they allow it
What are your ideas?

Comments

  • yahyah said:
    my country blocked all protocols offered by PIA but Chrome extension stile work and That's what worries me

    Maybe PIA Chrome extension broken or dns leak from Chrome extension and not give enough security so they allow it
    What are your ideas?
    The Chrome extension is an encrypted proxy, the proxy only encrypts Chrome browser traffic and nothing else. The extension blocks DNS leaks and other IP related exposures I wouldn't be worried if I were you, however your Internet service provider could be blocking VPN connections entirely depending on which country you're in. Once connected to the VPN or proxy your ISP and government cannot see what you are doing online.

    Download the latest release of the VPN software once more and try connecting using protocol TCP through Port 443.

    https://www.privateinternetaccess.com/forum/discussion/28774/the-ultimate-question-udp-vs-tcp-what-s-the-difference-which-one-should-you-choose#latest

    https://helpdesk.privateinternetaccess.com/hc/en-us/articles/226851548-I-have-trouble-connecting-or-the-connection-drops-frequently-changing-ports


  • I know it looks crazy but my country has blocked most VPN services include Pia TCP through Port 443 ,anyway thank OpenVPN for reply <3
  • This is definitely weird if your country normally blocks OpenVPN even on TCP/443. But my hypothesis on this would be that since the Chrome extension is an HTTPS proxy, it is completely indistinguishable on the wire from an actual HTTPS connection. Unlike OpenVPN which encrypts and sends packets mostly untouched over the network, a proxy connection can be buffered and form a continuous stream of data that looks no different than a normal download.

    On top of this, since the extension can only be used for web traffic, we end up wrapping other HTTP(S) connections within the HTTPS proxy connection (each request gets their own corresponding connection to the proxy server) so there's essentially no way to recognize it as a proxy even with deep behavioral analysis.

    The only thing that surprises me is that the domain name (https-REGION.privateinternetaccess.com) is not blocked, but maybe they just believe a lot in their VPN blocking abilities that they overlooked that. Who knows ¯\_(ツ)_/¯
Sign In or Register to comment.