Private Internet Access Firefox browser extension now available in beta!

OpenVPNOpenVPN
edited April 2018 in Software and System Updates
I felt this topic needed some special attention due to how many people have been requesting it in the last couple of months.  :) Login to the client control panel download the new extension.

Comments

  • p6021691p6021691
    Just so u all know i dont know if its a false positive or not....

    Upon installing this my Internet security package "Kaspersy Internet Security 2017" flipped out finding malware.
  • Omnibus_IVOmnibus_IV
    I would say that you got a false positive. Consider what PIA is doing and Kaspersy thinks it is malware, or a virus, or anything like that. I doubt that PIA would intentionally insert malicious code into their extension. I would tell the AV to ignore it.
  • p6021691p6021691
    How do u tell an antivirus to ignore it when it immediately deletes it?
  • RASelkirkRASelkirk
    OpenVPN said:
    I felt this topic needed some special attention due to how many people have been requesting it in the last couple of months.  :) Login to the client control panel download the new extension.
    I'd like to try this but I've uninstalled PIA from my computer due to it running at < 10% of my rated speed. So, is there a DL link somewhere?

    Russ
  • p6021691p6021691
    Login to your account and click beta programs.
  • RASelkirkRASelkirk
    Yeah, I got it figured The PIA UN and PW and not the forum UN/PW. :*

    Rus
  • abcabcabcabc
    the extension has been working great so far.
  • p6021691p6021691
    Ive contacted Kaspersky and they want a direct URL to the extension which ive stated i cannot give as its in a members area so im waiting for them to get back to me again.
  • RASelkirkRASelkirk
    Anyone know if this works with v50.1.0? All I get is a white block with no options...



    Russ
  • Max-PMax-P
    v50 might be a little too old to run the extension. It's a web extension so I think it needs new things that this version doesn't have.

    I just tried it on Debian which uses Firefox v52 and I have the same issue. Just reported to the devs.

    Works fine on v59 on my main computer however, so you should just need to update to the latest one and be good to go!
  • Omnibus_IVOmnibus_IV
    p6021691 said:
    How do u tell an antivirus to ignore it when it immediately deletes it?
    Sorry, I missed this post. It isn't delete unless you AV kills everything. It is usually just quarantined, You should be able to exempt it from you AV. Usually in the form of an exception,
  • Omnibus_IVOmnibus_IV
    edited April 2018
    On topic... I use Firefox 56 and will not upgrade until Firefox allows extensions they deleted. This PIA extension does not work and I suspected it would not. I tried Firefox 59 but it was really disappointing. The ability to do things seems to be curtained starting with Firefox 57. Would be nice if PIA could down grade the extension so it would work on earlier versions of FIrefox.
  • Max-PMax-P
    Extensions on older versions of Firefox are completely different, different code, different language even. Two different APIs.

    In order to make it work on older versions of Firefox, we'd have to essentially rewrite it for the old engine for a browser that's already EOL. It's unfortunate but it doesn't make sense to spend the resources to maintain two versions of the extension for something the vast majority of users will never use because they've already updated.


    As much as it sucks that lots of extensions are to be left behind, that transition was inevitable. Extensions could just poke at the browser's internals at will, so any major change to the rendering engine would break extensions anyway. This leaves the problem that Mozilla had to either stick with the old engine and the technical debt that comes with it but remain compatible. Or they do the significant changes that are needed to stay relevant, but break extensions, potentially multiple times.

    WebExtensions solves that by abstracting the internals away behind a standardized API that you can maintain the stability of, but that comes with the cost that on top of breaking everything, what you can do is limited by the API. But at least now if an "HTML6" thing happens, they can swap the entire engine again and not break a single extension in the process. Making the old engine's internals an API and translating the old to new and back is technically possible, but doing so would be super tedious and most likely buggy and slow.


    Hopefully the features you miss gets ported to the new Firefox soon enough so you can use our extension as well eventually :)
Sign In or Register to comment.