Updated Mac & Windows Client v.56 Released
Hey all!
We've just released updated versions of our Mac and Windows VPN applications, which you can find here:
SHA-256 Checksums:
installer_win.exe: 91eb5bd0381d48e8172d5fa48c7284b656c1953204f6c31ac51d2c45ae03cb30
installer_osx.dmg: 015d3e22d04e128cffcf62434c484719b16593bc29071fbb931c4dff5ccbfe62
Changes since v.55:
- Allow localhost communication while connected to the VPN (apps that use this feature, such as iTunes, should now work) [Windows]
- Allow communication with other hosts on the same network while connected to the VPN (e.g., connecting to your local printer should now work) [Mac]
- Add "Small Packets" option to help connectivity on some networks (disabled by default)
We thank you for your continued support.
Sincerely,
PIA
Comments
Can someone explain how this works? I would have thought smaller packets would increase latency, thus hinder throughput.
Just curious.
I would love to hear more details about this. If it works as I presume, what size does it use?
Also interested in the packet size used when the small packet option is checked.
Mike offered no defense of this configuration. However, he offered two alternatives: 1) use a different VPN client (e.g., Tunnelblick) or manually reenable the firewall after each OS boot.
Mike reported that this configuration will be changed in future versions of the PIA client.
PIA, you're supposed to be a security company. How can you claim to have our security interests at heart while disabling our firewalls? This makes absolutely no sense.
I mostly use Viscosity, so I don't have to worry about having my firewall being taken down without my knowledge or permission; but when I do use the PIA app I'm running v. 49. At least that version is reasonably stable and doesn't shut down your firewall. That's what I'd recommend to all OSX users do -- either don't use the PIA app at all, or if you do dial back to v. 49
Like I said before, it will be a huge plus to VPN client itself if you will integrate a new option called "Gaming Mode" under "Small Packets" with instructions "Exclude origin, steam, uplay from VPN" something like here see the image
I just wanted to clarify a few questions that i've seen some users asking here, about the new changes in v56.
- The small packets option. What this does is changes the --mssfix directive in the .ovpn configuration to statically use 1250; this can help on some networks to improve stability, but isn't necessary in most situations. It was added as a way to improve overall functionality on some networks, where disconnections may be occurring intermitently; use of this feature may help to reduce or resolve that issue in some cases.
- The firewall in Mac OS X. In order to guarantee security, we've had to change certain aspects of the code used to secure your service on MacOS. Part of these changes requires changing the state of the internal MacOS firewall during the app's operation. While the OS firewall is disabled, the connection's own security on the datastream immediately kicks in, and fully secures you while it's active. We're working to further expand upon these new changes, in order to eliminate their need to access/change the firewall's state; we hope to have a viable solution to avoid this short-term requirement, in a future build for our MacOS application. We apologize for the inconvenience in the interim, and appreciate your understanding and patience, while we continue work to keep your internet access completely secure and privatized at all times.
Kindest regards,
How about providing us with an "actually working" PIA software? ;-)
1) Create a small file that just contains the Port number when used on BitTorrent PIA capable VPN. This was promised by PIA Dev KYJelly in Sept 2014 https://www.privateinternetaccess.com/forum/discussion/comment/19922/#Comment_19922
Read the thread to see the reason why, as it help automation in getting the posts update in Torrent and other apps.
2) If a user selects to NOT start the VPN when windows starts, then please do not add the launch to the Scheduler. I always start the VPN by clicking a shortcut on the desktop but PIA adds an entry into the Win Scheduler to run PIA at logon.
3) The current action of launching the VPN starts Ruby in a Temp folder location. Could you an option to the settings to either launch Ruby the from a random temp folder or from the PIA_Manager folder in program files. Offering the fixed location will stop users having to modify the settings to allow Ruby though the firewall every it runs as the running from the temp folder requires setting a rule everytime.
4) Show the Version number on the main settings page and also in the popup tooltip in the notification area on hover.
5) Show in the settings page if an update is avaliable. It used to do this but stopped seveal version ago, so now you will have thousdands of users with outdtaed and exposed VPN connections.
These simple additions will greatly help users and also to devs.
4) VERSION NUMBER: The version number should be in at least these two important places:
* In the metadata associated with the installer file, as is normal with almost all other .exe installer files.
* At the top of the PIA settings page, in the same font. It should show when in Simple Mode, not just in Advanced Mode, so that the top line would read:
<icon> privateinternetaccess v. 56
The Peter Brown's tooltop suggestion would also be very helpful, or it could be on the right-click menu.
I spent 15 minutes looking for the version number the first time I needed it, and I eventually had to search the forum to get the clue about changing to Advanced Mode.
There is the further problem that the present font, besides being tiny, hardly distinguishes between 5 and 6. Yesterday, after returning from holidays, I checked my version number, and couldn't tell when it was:
v. 55 or v. 56 or v. 65 or v. 66.
I installed the new update v. 56, and could only barely discern that the two tiny digits were now different.
5) UPDATES: Further to Peter Brown's request for update notification, I would also like a PIA webpage that straightforwardly lists the recent updates. That page should give:
* Versions numbers, in a black title font
* The date each update was issued, in a black title font.
* A short dotpoint summary of the main changes, perhaps with a link to a more detailed account of those changes.
* A downloads button for the latest version.
* A link to some recent earlier versions in case a bug or incompatibility emerges.
It continues to amaze me how few software houses can put themselves in their users' shoes and write such a page. RoboForm is almost there, apart from access to older versions:
http://www.roboform.com/news-windows
Also, we have already bought the product and appreciate it, so we don't need to be exposed to PIA advertising everywhere we go on the website.
Can you please do something about marking and announcing new releases. I had no idea client v.56 for windows existed. I was suffering with major connectivity issues with v.53 since November/December (can't recall it's exact release date)
Suffice it to say, If I had not done the "live help" with Steve in your CS department, I would have never known. Thank you Steve for fixing my headaches with a simple recognition I wasn't using the newest client!! Not everyone who uses your service logs in here to check. Heck, I didn't until just minutes ago.
Thanks!
As for the change logs, if you weren't already aware, they are all available on our forums at https://www.privateinternetaccess.com/forum/categories/change-logs-etc . I understand what you mean about the visibility, and I will pass your concerns along to our Developer Team.
Cheers!