‍ ‍‍‍ᓭ cryptostorm ᓯ (@cryptostorm_is) 's Twitter Profile
‍ ‍‍‍ᓭ cryptostorm ᓯ

@cryptostorm_is

The VPN provider for the truly paranoid

ID: 108005122

linkhttps://cryptostorm.is calendar_today24-01-2010 13:51:15

30,30K Tweet

6,6K Followers

16 Following

‍ ‍‍‍ᓭ cryptostorm ᓯ (@cryptostorm_is) 's Twitter Profile Photo

New widget v3.58 is up at cryptostorm.is/cryptostorm_se… Only change is the built-in OpenVPN was updated to 2.6.10, and the OpenSSL to 3.2.1

‍ ‍‍‍ᓭ cryptostorm ᓯ (@cryptostorm_is) 's Twitter Profile Photo

Finished updating the OpenVPN on all our servers to account for qualys.com/2024/07/01/cve… still working on updating the tutorial pages, and adding IPv6 to everything

‍ ‍‍‍ᓭ cryptostorm ᓯ (@cryptostorm_is) 's Twitter Profile Photo

All the servers have been updated to OpenVPN 2.6.13 We'll hold off a bit on updating the OpenVPN our Windows client uses since none of the new features/bugfixes appear to be relevant to us, and some other changes will be made soon to that program anyways so we'll just wait until

‍ ‍‍‍ᓭ cryptostorm ᓯ (@cryptostorm_is) 's Twitter Profile Photo

cryptostorm.is/blog/port-stri… Port striping v3: Improved SNAT to address Port Shadowing (and more), isolated entry/exit IPs, better balancing and separation, hardened rulesets, more IPs for WireGuard users, and other changes

‍ ‍‍‍ᓭ cryptostorm ᓯ (@cryptostorm_is) 's Twitter Profile Photo

Just a heads up, we're going to be getting rid of these servers: ireland, madrid, denmark, bulgaria, rome, slovakia, latvia, mexico, and nc (North Carolina), mainly because their low usage doesn't justify their costs.

‍ ‍‍‍ᓭ cryptostorm ᓯ (@cryptostorm_is) 's Twitter Profile Photo

We replaced our 1 Gbps Atlanta and Chicago servers with 10 Gbps servers. The new IPs have already been added to the DNS. Those of you only using IPs in your configs need to update to the new ones.

‍ ‍‍‍ᓭ cryptostorm ᓯ (@cryptostorm_is) 's Twitter Profile Photo

We accidentally broke transparent .onion access for WireGuard users in cryptostorm.is/blog/port-stri… at "Tighter leak prevention in iptables". An exclusion was needed for tor's VirtualAddrNetworkIPv4. The transparent .onion (and .i2p) feature now works again for WireGuard users.