V.39 Changelog

meno

Changes in Version 39:

- fixes the connection issue with the Kill Switch where the app would sometimes take longer to connect after disconnecting.

Download here.

edit:

- after installation, the client will be labeled incorrectly as V.38. We are aware of this label error and the client will be updated to reflect properly shortly. Sorry guys. Fixed.

MonteCristo

I've just installed it and it doesn't connect at all!

meno

Hello,

Sorry to hear about this inconvenience. Will you reach out to our helpdesk to see if there is anything we can do to fix your connection issue? We would like to, at least, track common issues.

Best,

Masashevich

Cannot connect too with this new version, was fine before for years. Gonna roll back to old one.

Masashevich

Now it shows that connected, but does not provide different IP, it looks like it does nothing, i still has my ISP address. With any gateway

DeathStalker

I'll wait till we get more feedback on it .......

martywd

Strange?  Other than the wrong version number noted by @meno, I'm not experiencing any of the issues others describe here?

The 'VPN Kill Switch' functionality does indeed work for me as advertised _without_ blocking LAN connections from other machines on my network regardless of whether the VPN Client is active, or not.

FWIW, I'm running Win7 64-bit.
md5 checksum on the installer file:
\download\vpn\pia\v.39>fciv installer_win.exe
//
// File Checksum Integrity Verifier version 2.05.
//
04360812ea571a36f18b669203d3f6df installer_win.exe

\download\vpn\pia\v.39>
.

Asguardian

Working well for me thus far. V39, OSX 10.9.4.

I haven't restarted yet so I will see tomorrow if a reboot will yield the same good results. Will report back if not.

heyitsme

@martywd - The MD5 hash that you are showing above is the hash for Windows v38  :-?

Here are the hashes for v39 (first version)

CRC32: 65E4A2A0
MD5: BF4700D7B8E0F436A18F6BCD245D30FC
SHA-1: F44AF866A0884A2AD22F91668C74B5154FBD876E
SHA-256: 085CAF9D0D261BEAA5BE95464C3BFB99DA7590CD72F3B9C56EA40FC337F182F8

Can you check it again?

Masashevich

Was my fault, I installed all updates for windows (7) and now pia works fine again.

heyitsme

Was my fault, I installed all updates for windows (7) and now pia works fine again.

Good to know. I was going to wait until the corrected version arrived, but I got impatient. So far, no problems, but I don't use the Kill Switch anyway.

martywd

@martywd - The MD5 hash that you are showing above is the hash for Windows v38  :-?

Here are the hashes for v39 (first version)

CRC32: 65E4A2A0
MD5: BF4700D7B8E0F436A18F6BCD245D30FC
SHA-1: F44AF866A0884A2AD22F91668C74B5154FBD876E
SHA-256: 085CAF9D0D261BEAA5BE95464C3BFB99DA7590CD72F3B9C56EA40FC337F182F8

Can you check it again?

Dang!  Both the download last night and then again this morning gave that other checksum.

Just downloaded again.  This 'new' v.39 does match the checksums you listed.  (I checked them all on one of my *nix machines).  Using M$'s checksum utility which only does md5 and sha1 windows users should see something this (as I type this!):

\download\vpn\pia\v.39>fciv -both installer_win.exe
//
// File Checksum Integrity Verifier version 2.05.
//
                MD5                             SHA-1
-------------------------------------------------------------------------
bf4700d7b8e0f436a18f6bcd245d30fc    f44af866a0884a2ad22f91668c74b5154fbd876e installer_win.exe

\download\vpn\pia\v.39>

Of course this will all change again if the PIA Devs do more fiddling?

Nothing else has changed since my previous post.  The 'VPN Kill Switch' functionality is still working as describe earlier.  And now the 'Settings' window indicates:  v.39 .

That's about all I got.
.

OmniNegro

Here, this is freeware for non-commercial use. Windows and Mac versions. (Linux has better tools built in.)
http://implbits.com/HashTab.aspx

It is certainly a step up from the M$ checksum utility.

*Edit* That tool lets me easily generate hashes in a wide variety of formats. Just as an example, the v.39 Windows PIA client has these hashes for me at the moment.
Adler32: 0AE96EBF
BTIH: 74C4D99379102933FD5AFEA3C36A5EEF52E46EAD
CRC32: 65E4A2A0
ED2K: 9553095C92AAF94162B9EE802FB35E95
GOST: 7D11BEF3EB6CFC1695E3A4E301DA31CB54E170454778B6E177B7D849311A4010
MD2: 2072DE4B3F193B8950F35C6311C97A97
MD4: 3FFC4F1E02E6C2170C83868C3DC7C7D1
MD5: BF4700D7B8E0F436A18F6BCD245D30FC
RIPEMD-128: 42CD2FAAE2EC584945D0D215422DF66C
RIPEMD-256: 60F421EAF23FF4E6DDBE4CCC66BDA466B62A62C25F0FE5037B7C25166F49A338
RIPEMD-320: 439A1632DFC23DC64FBE5E06C1D81E851C7CA5481D081D77DBCF4669D1D136C9C9BC801E55EBC4C9
SHA-1: F44AF866A0884A2AD22F91668C74B5154FBD876E
SHA-256: 085CAF9D0D261BEAA5BE95464C3BFB99DA7590CD72F3B9C56EA40FC337F182F8
SHA-384: 4099AB323FF6A3DC815445CC22DD50172FAE7E1EFA863101B15655349562BB8EBC995656ACD04B201D61CD464054202F
SHA-512: 65716CBC9D640C0AD69088FBD56466667DEDD8A273D6178AEAC0DB2A70C73DCBD8629041C47E7E53A51C3B3731E79769AB7F24008200EAFE46325918D3C2FAF4
SHA3-224: 4E02067D71759A644DA7C5D68A454B79518F0B30E356DD519C882E40
SHA3-256: C4DC3842F2CBC3A78AD7CE5A822FC7241FA2AD11BBD6219E0E06DE1CA2960A0B
SHA3-384: 6E0804BF9F4FFF02CEEC88B1AE5B57930594795E4940A7BAF79098756D3A35332585C733D165D541668EC3D6107C9571
SHA3-512: 77A30E1D9AFB51487D73FB50774A4B1678656473136FB0D01D1F8F5992D03322E8930B3A0876B9341AC519266673F44CED66170EEAAD21F617BCBDCA4D53C86E
TTH: NGIAUGMKSYXS3A2BFWSR2TRE6QY4GQVDR54CHXA
Tiger: E4E473437DF01993DDED97653CAC2D1452E1C1009BB04BF7
Whirlpool: 323A4FDBC7343579DD73117E2EB21D4F162A50280AFBA5A0E9A6204A397AA8FEB4FF8155CB029977C2733DE7B117B89B0E4D221C52467988D99F8B1AA6CFEB70

While only a few are ever going to be used by most people, it is certainly nice to have all the options.

DeathStalker

Interesting that v.38 still isn't prompting for an update.

Either way, I'll wait till the last changes are made (hopefully soon).

Asguardian

Update: I restarted my mac when I came back from work this evening and lo and behold it connected straight to the VPN using the new v39. The reason I mentioned that it is it would rarely connect, it would just sit there and stay gray in my menu bar. I will have to put it through many more shutdowns and restarts to see if it sticks... will report back. Kill Switch is working as it should!
OSX 10.9.4 v39.

heyitsme

Here, this is freeware for non-commercial use. Windows and Mac versions. (Linux has better tools built in.)
http://implbits.com/HashTab.aspx

@OmniNegro I think I neglected to say thanks for this link. I downloaded it when you posted it previously, and I like it. So, thanks! ^:)^

I have another hash checker somewhere on my system, but it's much easier to just get the hashes from the file properties menu than to try and find the other utility when I need it.

OmniNegro

Here, this is freeware for non-commercial use. Windows and Mac versions. (Linux has better tools built in.)
http://implbits.com/HashTab.aspx

@OmniNegro I think I neglected to say thanks for this link. I downloaded it when you posted it previously, and I like it. So, thanks! ^:)^

I have another hash checker somewhere on my system, but it's much easier to just get the hashes from the file properties menu than to try and find the other utility when I need it.

You are very welcome. I too love how easy it makes hashing files.

Asguardian

Update: at least 3 more restarts and shut downs. PIA connects on login every time, kill switch still working well. This v39 is the best for me so far.
Thanks for fixing it!

OSX 10.9.4 v39.

Baine

Is this the right checksum for the Mac installer?

md5 2c849d9422ae382fcc1b6221d7635b2d

sha1 8190c8e75a31a92d0adc13ad6b5c5b8e45b46014

OmniNegro

Is this the right checksum for the Mac installer?

md5 2c849d9422ae382fcc1b6221d7635b2d

sha1 8190c8e75a31a92d0adc13ad6b5c5b8e45b46014

Yes. Here are the full list of hashes for the Mac v.39 installer.
Adler32: F61D31A3
BTIH: 73CE41625C864E70F80A6CCA94DC87621DEF9162
CRC32: 190E6765
ED2K: 63B8CCF67EB1742444D86742E739ACBB
GOST: CC4A685567811C9FAAB552BAF517E4014D75F2B9D40BD95DEA6F0E4A1AE147E5
MD2: 5ABFC627A087B08561D54595B8029007
MD4: F34AF3EBC8861D7CA4CE441EF4F4F675
MD5: 2C849D9422AE382FCC1B6221D7635B2D
RIPEMD-128: 916A2683FAEE7595F23FF72B199F6D01
RIPEMD-256: 13DE6FA103716B5B602C999AA3CCE02554D44FD462ED5879A1C6F0B73DE370D0
RIPEMD-320: DBD2C4CA14CC9C9CBAD2238135829FC38468D5562714EF0084335585F44DED93FCD4F4CD25FD613E
SHA-1: 8190C8E75A31A92D0ADC13AD6B5C5B8E45B46014
SHA-256: A71E496289FC86807367D25597BA413B108E4CB3B972082C357A54446B2F545B
SHA-384: 562B3E3588E733DC93D871BF3F9A934ABB1C1E5F9B673A396EFFAF7FF41F3FC69DD57C053B6BD2A87323293C41F7105A
SHA-512: 5E1BB9CD97AC0D4EC83F9F2AACB8C3A9D59F11EDA436DAE4A9ABD2BCEE54762D5C9DF3EBAC02304DE8ADD4204468BC7A74D1592E426FC31449503551DBFD24CE
SHA3-224: 99980575478056837824FF7678552D2484431694B8E9C640E2197BB7
SHA3-256: FF8B9D302F6A5AD9C42F9AD4C1E4D956D3E7014CACE9302593281588EA3EE405
SHA3-384: F75935CC43D1DA9EF5E932163DAE90FF75E5798145E3CB8520FADC4B709E28DB56EE913AF96767CB89CE4DB9E315FF3C
SHA3-512: 8F66197A4B7BDFE7A92C803E9755B9CF30EB8D1021AA59637B98F5906AB1FC2C790A63C7632F80E0F6B06BBD9543493B4D0D8A3D73DD5428AC4F1DB169974797
TTH: IBH6BDLQFBEOFZNRX6GT2EAPCM3GQOBOKCIJUUY
Tiger: 27EA593DE23FE04890EB6FBF9D027C272C136A63AFF87E99
Whirlpool: 080E853BB9A02786F7B940AFAD410E2C890892732634AA9540AD1515EEB5B615CBE627BF4E97C2DBCF492A18EE38F895B0DEC9C4ABDEBC14AD106AE3664A7959

Asguardian

UPDATE: After several days of testing, it is back at doing what it did in the past, the app loads at startup but does not auto connect. I would say it's 50/50. Kill Switch seems fixed though.
OSX 10.9.4 v39.

VPNTester

V.39 does not reconnect and kill switch does not work properly on Win XP.
Back to version 36... :-(

nezzz

Still waiting for a OSX 10.10 compatible version.

heyitsme

I hate to be a b**** about it, but how long does it take to correct the version number? It didn't take this long last time.

** Post edited due to vulgarity by Goldstein

meno

I hate to be a b**** about it, but how long does it take to correct the version number? It didn't take this long last time.

** Post edited due to vulgarity by Goldstein

The issue was resolved immediately and your client should state V.39

heyitsme

I hate to be a b**** about it, but how long does it take to correct the version number? It didn't take this long last time.

** Post edited due to vulgarity by Goldstein

The issue was resolved immediately and your client should state V.39

My apologies @meno. "> I was expecting to have to install a new client, so I kept checking the original post for an update and didn't see one.

To be honest, my eyesight is so poor, and the font so small and light in the client, that I couldn't tell that it had been changed. Sorry 'bout that.

meno

No worries @heyitsme. I should have updated the OP (now updated). Sorry about that as well

VPNTester

Also, v.39 was disconnecting at least once a day vs v.36 goes for days at a time!

DeathStalker

Well, no problems SO far with v.39 <keeps fingers crossed>

Like I think I mentioned in another post, it would be nice to have a Connected Time in the GUI (even as just a hover tooltip) - and yes, I know one can look at the LOG file and get the info.

Thanks!

kcimpulse

Just like VPN Tester my v.39 Disconnects at some point during the day but still shows connected. Kinda frustrating.

rmay1216

V.39 for me also is disconnecting a few times a day.