Freemor

People need to read...

Freemor at

The Threat Is Already Inside

And nine other truths about terrorism that nobody wants to hear.

https://foreignpolicy.com/2015/11/20/the-threat-is-already-inside-uncomfortable-truths-terrorism-isis/ 

Excellent and honest write up on the situation.

Arcee, Arcee, Arcee shared this.

A little about Russian censors:

$ wget https://foreignpolicy.com/2015/11/20/the-threat-is-already-inside-uncomfortable-truths-terrorism-isis/
--2016-01-07 19:52:04--  https://foreignpolicy.com/2015/11/20/the-threat-is-already-inside-uncomfortable-truths-terrorism-isis/
Resolving foreignpolicy.com (foreignpolicy.com)... 192.0.79.32, 192.0.79.33
Connecting to foreignpolicy.com (foreignpolicy.com)|192.0.79.32|:443... connected.
ERROR: The certificate of ‘foreignpolicy.com’ is not trusted.
ERROR: The certificate of ‘foreignpolicy.com’ hasn't got a known issuer.
The certificate's owner does not match hostname ‘foreignpolicy.com’

Ok, my provider replace certificate to fake one to filter my traffic. Why they censored this site? Let's check https://antizapret.info/index.php?search=foreignpolicy.com: Prosecutors add two URL's from heavy.com into list of forbidden resources in Russian Federation. heavy.com and foreignpolicy.com shares same IP addresses. I open foreignpolicy.com through https, so provider in this conditions can not easily filter my GET requests and they use MITM attack to not allow me to look at two forbidden URL's.

Sigh, can I trust to provider or I must use proxy from my foreign VPS? I choose proxy.

mnd at 2016-01-07T15:14:01Z

Wow, thanks for the info there. Had no idea that there would be an issue there. It's always good to have people reporting where the edges are.

Freemor at 2016-01-07T18:50:06Z