Just built a new widget v3.0.0.72 that includes code that now saves that connect timeout value (Under "Options" -> "Connecting") so it's remembered on restart.
Also OpenVPN/OpenSSL binaries/libraries upgraded to 2.3.16/1.0.2l.
Latest hashes for
https://cryptostorm.is/cryptostorm_setup.exe -
crc32: 6fe993a6
md4: 2c09931daadb7ac8e88401422364c0ea
md5: 47a1d8d88fbe1c9b8655669af25f65a9
ripemd160: 0d233cd5f3c4842c772df06f2ebb4d42eccf93d0
sha1: b87c4cf014e70b8eabb462d2330388f9f87ce4a8
sha256: f9cabb029ea14a30feff44a33ed2ec8b73f9508d5840eb0bb495b7ab6bf4e083
sha384: ded51f638c8cef40a9a2ea268360d90ef213e6bf049a5aa5e427f027bc867ea2e65e767a332d9a564110b168903bab00
sha512: 3b6f4e4c14880f77dd980edcd9bbb414d83ed183a8dce91c9801858d6cedc53ceea1acb39bb567fa4f0b0e8ae3aded3f03858790d6efdd3805a7a9f687a828e0
wpool512: e407fe382d3f31d3189b0f237feb41a6541e7be1e5f1dfbfa75d6baedeae1ff815af2d32f2a3a8f6b5c16ddee18926443a5364e0d096150682bf9c1179aa4342
@KungFuChe
XP is no longer supported. Anyone still on XP will have to stay on the older v2.22, which won't receive any new updates, unless some horribly vulnerable issue is discovered in the openvpn/openssl that version uses.
It's usually a bad idea to provide backwards compatibility for an OS version that stopped receiving security updates several years ago.
I do plan on doing more tests regarding the different ways internet can be disconnected and how to detect it so the widget responds accordingly.
Same goes for the different CPU features and architectures, and the systray issues that seem to vary by Windows version.