Page 1 of 1

current 'config' files for cryptostorm network connections (rev. 1.4)

Posted: Wed Dec 25, 2013 6:05 pm
by cryptostorm_team
THESE FILES ARE NO LONGER UPDATED HERE! FOR THE LATEST CONFIGS GOTO our github repository


Members connecting via our Windows network access widget do not need to manually download or implement these configuration files, as they are pre-packaged with the widget installer.


This thread exists to serve as a one-stop location for the most current version of the client configuration files for cryptostorm. As new versions complete alpha (internal) and beta (community) testing successfully, they'll be swapped into this post - so that there's always the most current approved configs (and only the most current versions) here in this thread.

Note that all config files in this post have, as of today (12 January 2014) been upgraded to Hostname Assignment Framework compliance. This delivers vastly improved session security, resilience, and flexibility as our network continues to grow and expand.

A much deeper discussion of client configuration files, as well as archival copies of earlier versions, can be found in a separate, parallel thread. To ensure that discussion stays in one place, this post is locked & does not accept replies. Please, if you've got feedback or questions or comments on the config files, post them in the parallel thread - thanks!

These configuration files vary only in the choice of exitnode clusters embedded in them, and in their tuning for use with particular operating systems. Otherwise, they are identical to each other. Selected cipher suites, session parameters, and authentication methods are the same. Windows-based members connect to dedicated "instances" of our servers, and mostly everyone else can use the configuration files labelled "Linux." (we used to call those "raw" files but it was a terrible name and so we've moved to just using "Linux," even though it'll support BSD/OSX, and many other operating systems)

You will notice that there's two different ways to do broad-spectrum, "randomised" connections to our global network: dynamic, and settled. We can dig deeper into the differences in these models elsewhere; for here, it's best to think of the "settled" versions being less likely to "jump around" between geographically dispersed nodes during routine network interruptions. Conversely, "dynamic" balancers will be more aggressive in effectively randomising the node to which each session connects - including routine reconnects. Some folks like the extra variability and attack-surface hardening of the dynamic model; others want a bit more stability of node selection and thus the "settled" balancer does well for them.

Otherwise, network connections are made based on exitnode clusters as defined by a city (or, in a small number of cases, a geographic section of a larger country); this, again, relates to the HAF approach to network resilience, and is able to help ensure the network is always available, even with the routine ups and downs of individual nodes.

new Singapore anchor exitnode, just provisioned
cstorm_linux_singapore_1-4.conf
(5.57 KiB) Downloaded 1446 times


cstorm_linux_london_1-4.conf
(5.34 KiB) Downloaded 1334 times

cstorm_linux_smoothed_1-4.conf
(5.48 KiB) Downloaded 1344 times

cstorm_linux_stpetersburg_1-4.conf
(5.37 KiB) Downloaded 1172 times

cstorm_linux_iceland_1-4.conf
(5.32 KiB) Downloaded 1741 times

cstorm_linux_dynamic_1-4.conf
(7.5 KiB) Downloaded 2558 times

cryptofree_client_android1_4.conf
(5.26 KiB) Downloaded 752 times

cstorm_linux_paris_1-4.conf
(5.33 KiB) Downloaded 1367 times

cstorm_linux_frankfurt_1-4.conf
(5.34 KiB) Downloaded 1279 times

cstorm_linux_montreal_1-4.conf
(5.34 KiB) Downloaded 1161 times

cstorm_linux_uscentral_1-4.conf
(5.33 KiB) Downloaded 1370 times

cstorm_linux_uswest_1-4.conf
(5.32 KiB) Downloaded 1343 times



For our no-cost, capped-speed cryptofree service:
cryptofree_client_linux1_4.conf
(5.42 KiB) Downloaded 1228 times

cstorm_linux_lisbon_1-4.conf
(5.29 KiB) Downloaded 1026 times


Mac/OSX optimised:

cstorm_mac_smoothed_1-4.conf
(5.37 KiB) Downloaded 743 times

cstorm_mac_iceland_1-4.conf
(5.21 KiB) Downloaded 1346 times

cstorm_mac_paris_1-4.conf
(5.22 KiB) Downloaded 3630 times

cstorm_mac_montreal_1-4.conf
(5.33 KiB) Downloaded 2500 times

cstorm_mac_frankfurt_1-4.conf
(5.23 KiB) Downloaded 702 times

cstorm_mac_uswest_1-4.conf
(5.21 KiB) Downloaded 4094 times

cstorm_mac_uscentral_1-4.conf
(5.22 KiB) Downloaded 686 times

cstorm_mac_london_1-4.conf
(5.23 KiB) Downloaded 2072 times

cstorm_mac_stpetersburg_1-4.conf
(5.26 KiB) Downloaded 560 times

cstorm_mac_singapore_1-4.conf
(5.46 KiB) Downloaded 627 times

cstorm_mac_lisbon_1-4.conf
(5.18 KiB) Downloaded 571 times


Coming soon, or in short-term re-provisioning status:

list of HAF-compliant --remote parameters

Posted: Thu Jan 22, 2015 12:26 pm
by Pattern_Juggled
There's been a request (via twitter) to have a tl;dr list of the current, HAF-compliant (1.4) --remote connection parameters, for those who prefer to simply do edits to their client-side conf's rather than downloading new ones (or using the widget). As such, I'll post this here and ensure it stays current.

note: each of these entries can be expanded into any of the four top-level domain (TLD) resolvers we are currently using for this process:

    cryptostorm.net
    cryptostorm.org
    cryptostorm.nu
    cstorm.pw

So, for example, linux-balancer.{TLD} unpacks to these four entries:

    linux-balancer.cryptostorm.net
    linux-balancer.cryptostorm.org
    linux-balancer.cryptostorm.nu
    linux-balancer.cstorm.pw

This procedure is explained more fully in the complete HAF whitepaper, for those curious as to what purpose it serves and why we've developed this approach to resolver-based network resource identification.

Finally, these for linux; the exact same resolvers are always available for windows connections: simply replace "linux" with "windows"

    linux-balancer.{TLD}
    linux-singapore.{TLD}
    linux-dynamic.{TLD}
    linux-stpetersburg.{TLD}
    linux-lisbon.{TLD}
    linux-iceland.{TLD}
    linux-uswest.{TLD}
    linux-uscentral.{TLD}
    linux-frankfurt.{TLD}
    linux-paris.{TLD}
    linux-montreal.{TLD}
    linux-london.{TLD}

Cheers,

~ pj

Re: current 'config' files for cryptostorm network connections (rev. 1.4)

Posted: Fri Jun 26, 2015 5:51 am
by jlg
We've just updated https://github.com/cryptostorm/cryptost ... tion_files to reflect the current config files.