Can't connect to your favorite node? look here

[cryptostorm_support]

Current status:

Chisinau (Moldova) is up and running again. The following nodes are unavailable:

linux-balancer.cstorm.pw:
London (UK)
Canada
Frankfurt (Germany)

windows-balancer.cstorm.pw
London (UK)

We have some servers that are unavailable at the moment due to different reasons: abuse and DCMA.
DCMA we all know, abuse can have different forms like DDOS, SQL injection attacks/scans etc.

We are in the process of negotiating with the data centers to bring these 'abuse' nodes up.
In order for them to release these nodes again, we need to indicate how we will prevent this kind of abuse in the future.
As we stick to our principles, we will not start to log or take other actions that would be intrusive for the privacy of our customers,
instead we will use techniques like iptables/IDS to prevent this. This means that the nodes will be marginally less traffic neutral.
Normally this shouldn't be noticeable for the users that are not into this type of abuse (quoting df: noisy as hell hack attempts).

Further updates will follow ...

[wpaschukat]

Thanks for the update and the good work. Appreciated.

[cryptostorm_support]

update: linux-cantus is available again ... .

[privangle]

Hi,

linux-frankfurt is working for me;

linux-canadawest and linux-london are off.

I am dissapointed with the fact that some people use CS for abuse.

[parityboy]

@privangle

So am I but just like Tor, any kind of anonymizing infrastructure will attract and breed this kind of behavior. Unfortunately with the current state of human kind, it's inevitable.

[hollyg]

Today (or recently, IDK last time I checked) Netflix is blocking (linux) all the US servers. I realize this is a slightly different problem, but is there any way to get around this?

[privangle]

@parityboy

Yes, I understand.

I am happy to see that London is on again.
Canada is still off, and Italy is off for the moment.

Then I have a (perhaps stupid) question concerning the configuration files:

I understood that the actual files/data are under github and what I don't understand is that the structure of the files there is quite different as the xxx.conf files I downloaded in the past and I'm using.

When I click on cstorm_linux-chisinau_udp.ovpn for example, I could copy/paste the text and store it in a text file. Or I click on

cstorm_linux-chisinau_udp.ovpn -> Raw

and see in the browser the configuration file in a text format (see here).

Could I in spite of the difference to my .conf files store the "raw-text" in a file, import the file in in my Network Manager and it would work ? (Linux)

I apoligize if my question is in the wrong thread. Tell me and I put the question otherwhere else.

When I find a difference to my .conf files on github, I adapt my .conf file to the changed data found on github and store the file as .conf, so the structure of my .conf files remains the same. Is this the good way to do? For me its some confusing.

Thank you.

[LoveTheStorm]

Canada and Italy work good for me.

[parityboy]

@privangle

Yes it should work, .conf and .ovpn are basically text files anyway.

[Guest]

I hope this is not too much off topic but it seems as if the new IDS of the London node interferes with linux updates. For example a "sudo apt-get update" gets stuck at "fetching headers". I tested Germany and Switzerland and those do not cause such errors.

[df]

Guest: I just removed the rules that caused the current snort alerts, a lot of them were clearly false positives (only 2 or 3 looked like legitimate attacks).

try apt-get now.

[privangle]

@parityboy

Yes it should work, .conf and .ovpn are basically text files anyway.

I tested it, I copy/pasted the text of the Raw-file in a textfile.conf, import textfile.conf into my Network Manager. It works like a charm. Nice!

Thank you.

[Guest]

Guest: I just removed the rules that caused the current snort alerts, a lot of them were clearly false positives (only 2 or 3 looked like legitimate attacks).

try apt-get now.

It works again. Thanks for the fix!

[Raka74]

London isn't working for me is it down?

[parityboy]

@Raka74

Yep, it's down. Either flaky RAM or a flaky RAM slot, apparently.