New Client Installer V. 45 (Win & OS X)

Hey everyone!

I know I have been quiet lately and I apologize for this.  Big things are on the way and I have been pre-occupied with our back office.  I have been noticing a lot of issues with port forwarding and although I didn't mention anything here, I did go ahead and alert our dev team.  I hope this helps the lot of our members with these issues~ :)>-

sha256 checksum:
 windows: c9e2468d0e7d05c05f620ee0d049d24979a86d059ab2603288b33577744263aa
 osx: 94c3160d20ad3900f8c63d568fb4e4e5687d0511ed12a7d9f72807e7ec41a363

Change log:
Update Thu Oct 16 2014 - v.45
   - Fixes issue with port forwarding
«13

Comments

  • Hi KYJ!  Glad to see you're back!   :)

    v.45 is now showing the port and pf looks to be working again  :)


    Here's hoping those "big things" are also GOOD things!

  • edited October 2014
    Thanks for the new client. ^^

    Sadly, on OSX I am now getting the same constant drive writes as I did on Windows with the PIA client, so reverting to v43. ;_;

    For anyone else with this Ruby drive write issue on OSX I have uploaded v43 to Dropbox:
    https://db.tt/JUv7hyCu

    SHA256:
    a0735b7db15c9784aa1b1877ed0ba6fc2caac6dc279a9c3471376d55d7247db0

    Was port-forwarding broken in v44? I never tested v44 on OSX.
  • As usual, anyone not getting the right version can grab the copy I put in my Dropbox VPN cache.
    PIA VPN Installer 45 Windows.


    CRC32: 76D1D1EB
    MD5: D780C04BD9283C0408F226517D5B5D84
    SHA-1: C10E78BC5B76F193CA81A6041AE4A09F84E06CA1
    SHA-256: C9E2468D0E7D05C05F620EE0D049D24979A86D059AB2603288B33577744263AA
    SHA-512: 5896DCBE173FAFA4FC3BFACC0C12BA7AE5AD02A6FC88D868E338B4E60934C6F9DA3CFA33DBFF1915E1A478D9DCECCE3940B29034E76BDEFBEA222C4D549C07CC
    SHA3-256: 4ECE98F5684863EE5235F266B130EF773B39B9B958C30E7A596475D7B92FBB88
    SHA3-512: BBB9C97CA80820600119725037113856496B65ABEAD1F8B4D25AF25EA4EE37E433E55A36F6044466E94692134C55415F46620C7EE60DE9404CD46C2FEB228FF8
  • Hey @grh!  OpenVPN which our client uses is not vulnerable.  Please see here: https://forums.openvpn.net/topic17268.html

    Also, the attack is only for cases where the attacker can manipulate the traffic going through the tunnel.  Just an FYI~ :)>-

  • Yes, @KYJelly good to see you back and bringing us a fix in the new client - which is also working fine for me. :D

    Hoping the "big things" get here by Christmas, I'm like a kid anticipating Santa at this point.
  • How is the Kill Switch working in this version?
  • How is the Kill Switch working in this version?
    v.45, when the 'Kill Switch' option is activated, for me in Win7, seems to be working as advertised ==>  https://www.privateinternetaccess.com/pages/client-support/#disconnectprotect

    .
  • I notice that v.45 is still creating a second instance of PIA_TRAY.EXE that repeatedly tries to close - you can't tell unless you look at the processes &/or have error sounds turned on.

    :(

  • Hey @DeathStalker!  Would you mind providing me a debug log so I can send it to our dev team?


  • is it normal to have 2 instances of pia_manger.exe running?  I see 2 of them
  • I'm running v.43 and it's just started not giving port forward numbers on any node I've tried, about 2/3 of them so far...

    More generally: is there any good reason for what seems like an unending stream of updates? Are they really necessary? If they are, why? Can't PIA get it right?  Or is a new general security issue being discovered pretty much every other day?

    Just that it looks unprofessional to be issuing updates all the time, makes users appear as unpaid beta testers.

    Make sense? Or am I being unduly harsh in my, er, ignorance?
  • How many updates is appropriate? Better question. How many updates does your OS have? This is just the nature of software these days. Every time you eliminate a million bugs you will doubtlessly find more that your fix to the last ones left behind. So the updates happen often.
  • Agree with Tripod, v45 would not have been needed if v44 was tested thoroughly before being released.
  • Ummm, still issues with v.45 as far as I'm concerned .........

    No updates would only exist in a Utopia - NO program, period, is ever released without updates ....

  • Agree with Tripod, v45 would not have been needed if v44 was tested thoroughly before being released.
    By this sort of logic, everyone should disable their antiviral software from updating, because if they had done it right the first time, they would have known about the malware developed after the last release.

    Again, this is just not the way software development works. Here is a quote I use elsewhere that applies perfectly here.
    "Debugging is at least twice as hard as writing the program in the first place.

    So if your code is as clever as you can possibly make it, then by definition you're not smart enough to debug it."

    This is the problem. What we experience with constant updates is merely the symptom of the problem. And there is another way, but few people want to spend the cash for a router to handle all encryption for them.
  • I'm running v.43 and it's just started not giving port forward numbers on any node I've tried, about 2/3 of them so far...

    More generally: is there any good reason for what seems like an unending stream of updates? Are they really necessary? If they are, why? Can't PIA get it right?  Or is a new general security issue being discovered pretty much every other day?

    Just that it looks unprofessional to be issuing updates all the time, makes users appear as unpaid beta testers.

    Make sense? Or am I being unduly harsh in my, er, ignorance?




    The issue this time was that some brainiac system admin decided to update the software package on the servers without testing and figuring out the impact of the updates on the users.  The .45 was a fix for that bad judgement.  It never should have been done this way.

  • Agree with Tripod, v45 would not have been needed if v44 was tested thoroughly before being released.
    By this sort of logic, everyone should disable their antiviral software from updating, because if they had done it right the first time, they would have known about the malware developed after the last release.

    Again, this is just not the way software development works. Here is a quote I use elsewhere that applies perfectly here.
    "Debugging is at least twice as hard as writing the program in the first place.

    So if your code is as clever as you can possibly make it, then by definition you're not smart enough to debug it."

    This is the problem. What we experience with constant updates is merely the symptom of the problem. And there is another way, but few people want to spend the cash for a router to handle all encryption for them.
    To make my point clear, V45 (for the Port Fwd only) problem was not needed if v44 was tested properly before release. As for all the other "Under The Hood" bug fixes, of course. I agree with what you said.
  • I disagree. The port forwarding was working fine in v44. There were apparently some server changes behind the scenes which made a client update necessary. I don't expect PIA to have anticipated whatever caused this problem back when v44 was coded and released.

    Anyway, what are we talking about, 3 minutes to install a new client? It isn't that big a deal to me at all.

    I once saw someone complaining about Firefox minor versions being released withing days of the major version release - we're talking security fixes - and it just made me wonder how anyone can complain when that happens. Perhaps they would rather have security holes unpatched than to take a couple of minutes to update. I don't understand that thinking.
  • so far so good with port forwarding and now regards to the "kill switch" I would like it changed from killing your internet on the computer to kill only the specified applications!   Any comments?


    Don..

  • so far so good with port forwarding and now regards to the "kill switch" I would like it changed from killing your internet on the computer to kill only the specified applications!   Any comments?


    Don..

    The VPN is only made to bind to the Network Interface. It literally has no way to recognize the programs running. Firewalls usually have that sort of capacity though, so perhaps it would be trivial with the right firewall to bind those applications with the right interface and lock them out of any others.

    But I know of no way to actually do that.
  • How is the Kill Switch working in this version?
    v.45, when the 'Kill Switch' option is activated, for me in Win7, seems to be working as advertised ==>  https://www.privateinternetaccess.com/pages/client-support/#disconnectprotect

    .
    Thank you for your input! Anyone else have seen the Kill Switch in action? :-)
  • How is the Kill Switch working in this version?
    v.45, when the 'Kill Switch' option is activated, for me in Win7, seems to be working as advertised ==>  https://www.privateinternetaccess.com/pages/client-support/#disconnectprotect

    .
    Thank you for your input! Anyone else have seen the Kill Switch in action? :-)
    Not recently, but last time I was using it, my ISP chose that as the time to reset my connection and assign me a new IP. It does work.
  • Thanks Omni :-)
  • Anyone else have seen the Kill Switch of version 45 in action?
  • I tested it, and it performs well just like 44 did on win7 64bit.  Yes and I did test this multiple times.
  • Anyone else have seen the Kill Switch of version 45 in action?
    Are you having a problem? For instance, does the Kill Switch not work for you? If you are just being cautious, unplug your router or modem while it runs and plug it back in. That will give you a clear example of it working or not.
  • I tested it, and it performs well just like 44 did on win7 64bit.  Yes and I did test this multiple times.
    That is what I wanted to hear! :-)

    Thank you!
  • Anyone else have seen the Kill Switch of version 45 in action?
    Are you having a problem? For instance, does the Kill Switch not work for you? If you are just being cautious, unplug your router or modem while it runs and plug it back in. That will give you a clear example of it working or not.
    Some of the version DID NOT work properly, so I rolled back to v.36 which works OK for me on Win XP, and before doing an upgrade to v.45 I wanted to make sure that it worked for other people.

    Some years ago, I stopped believing that a newer version of software is better than the old one ;-)
  • so far so good with port forwarding and now regards to the "kill switch" I would like it changed from killing your internet on the computer to kill only the specified applications!   Any comments?


    Don..

    The VPN is only made to bind to the Network Interface. It literally has no way to recognize the programs running. Firewalls usually have that sort of capacity though, so perhaps it would be trivial with the right firewall to bind those applications with the right interface and lock them out of any others.

    But I know of no way to actually do that.
    I know PureVPN did as well as IBVPN and HMA per application not the whole network...
  • I would just like to point out that my PIA client (v43) never prompted me to upgrade to v44 or even v45.

    It was only because I could not get a port number these last few days on connecting to the Netherlands that I came to the PIA forum to see if it was an issue with Port Numbers. Here on the forum I find that there has been 2 PIA client updates since 7th October (2 weeks ago).

    Is the updater message in PIA client working?
Sign In or Register to comment.