20 Apr
2018
20 Apr
'18
12:57 a.m.
[This has been forwarded to a number of mailing lists, but in
case you haven't already seen it, you may find it of interest.
This copy was received from the NANOG list. - Brian]
Begin forwarded message:
From: Alexander Isavnin <isavnin(a)gmail.com>
Subject: [cooperation-wg] Massive IP blockings in Russia
Date: April 17, 2018 at 1:36:33 PM EDT
To: cooperation-wg(a)ripe.net
Dear colleagues!
I'm not pleased to inform you that RosComNadzor, a Russian Communication
supervisory body, has started blocking huge ranges of IPs belonging
to different cloud infrastructures, mostly Amazon and Google Cloud.
Those ranges include: 13.52.0.0/14, 13.56.0.0/14, 18.184.0.0/15,
18.194.0.0/15, 18.196.0.0/15, 34.192.0.0/10, 34.240.0.0/13,
34.248.0.0/13, 35.156.0.0/14, 35.160.0.0/13, 35.176.0.0/15,
52.0.0.0/11, 52.192.0.0/11, 52.208.0.0/13, 52.28.0.0/15, 52.58.0.0/15,
54.144.0.0/12, 54.160.0.0/12, 54.228.0.0/15, 54.72.0.0/15, 54.88.0.0/16.
Russian ISPs MUST fully block all traffic to such networks. The
list is frequently updated and gets automatically propagated to ISP
every once in a while, failure to block any address may result in
1500eur fine. The infrastructure listed above is being added to
the blocklist under 'counter-terrorist and counter-extremist' order
of the General Prosecutor Office, #27-31-2015/Id4082-15, issued in
2015 and often used for blocking an arbitrary unwanted content.
The real reason for such blocking is an attempt to cut access to
Telegram messenger, which refused to provide end-to-end encryption
keys to the Federal Security Service (previously known as KGB).
This is a case similar to San-Bernardino shooter's, where the FBI
was denied access to the shooter's iPhone, but courts in Russia
have made completely opposite decision. Telegram's infrastructure
is being blocked by a different decision by RosKomNadzor, #2-1779/2018.
Cloud infrastructures are being blocked for massive proxy and VPN
hosting used to dodge messenger blocking.
It is said, that more Apple and Google networks may be blocked soon
for apps updates and push notifications delivery for Telegram.
We hope to still have the global IP connectivity to keep you informed
about how the situation develops. Do not be surprised if some of
your services placed in cloud infrastructures will miss Russian
customers.
You can monitor the number of IP addresses, domains and URLs to be
blocked in Russia at the https://2018.schors.spb.ru/ page (run by
the famous ENOG community member Phil Kulin). Detailed information
(also via API) is available at the https://reestr.rublacklist.net
run by RosKomSvoboda civil society group.
Kind regards,
Alexander Isavnin
Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum
----- End forwarded message -----
20 Apr
20 Apr
2:02 a.m.
Denny,
Not sure how, or if, this will affect ‘us’. But thought you might find the info of
interest—as I did.
This was fwd from the UCSD guy who administers the AMPR.net <http://ampr.net/>
domain for the world in San Diego.
Jack
On Apr 19, 2018, at 10:57 AM, Brian Kantor
<Brian(a)BKantor.net> wrote:
[This has been forwarded to a number of mailing lists, but in
case you haven't already seen it, you may find it of interest.
This copy was received from the NANOG list. - Brian]
Begin forwarded message:
From: Alexander Isavnin <isavnin(a)gmail.com>
Subject: [cooperation-wg] Massive IP blockings in Russia
Date: April 17, 2018 at 1:36:33 PM EDT
To: cooperation-wg(a)ripe.net
Dear colleagues!
I'm not pleased to inform you that RosComNadzor, a Russian Communication
supervisory body, has started blocking huge ranges of IPs belonging
to different cloud infrastructures, mostly Amazon and Google Cloud.
Those ranges include: 13.52.0.0/14, 13.56.0.0/14, 18.184.0.0/15,
18.194.0.0/15, 18.196.0.0/15, 34.192.0.0/10, 34.240.0.0/13,
34.248.0.0/13, 35.156.0.0/14, 35.160.0.0/13, 35.176.0.0/15,
52.0.0.0/11, 52.192.0.0/11, 52.208.0.0/13, 52.28.0.0/15, 52.58.0.0/15,
54.144.0.0/12, 54.160.0.0/12, 54.228.0.0/15, 54.72.0.0/15, 54.88.0.0/16.
Russian ISPs MUST fully block all traffic to such networks. The
list is frequently updated and gets automatically propagated to ISP
every once in a while, failure to block any address may result in
1500eur fine. The infrastructure listed above is being added to
the blocklist under 'counter-terrorist and counter-extremist' order
of the General Prosecutor Office, #27-31-2015/Id4082-15, issued in
2015 and often used for blocking an arbitrary unwanted content.
The real reason for such blocking is an attempt to cut access to
Telegram messenger, which refused to provide end-to-end encryption
keys to the Federal Security Service (previously known as KGB).
This is a case similar to San-Bernardino shooter's, where the FBI
was denied access to the shooter's iPhone, but courts in Russia
have made completely opposite decision. Telegram's infrastructure
is being blocked by a different decision by RosKomNadzor, #2-1779/2018.
Cloud infrastructures are being blocked for massive proxy and VPN
hosting used to dodge messenger blocking.
It is said, that more Apple and Google networks may be blocked soon
for apps updates and push notifications delivery for Telegram.
We hope to still have the global IP connectivity to keep you informed
about how the situation develops. Do not be surprised if some of
your services placed in cloud infrastructures will miss Russian
customers.
You can monitor the number of IP addresses, domains and URLs to be
blocked in Russia at the https://2018.schors.spb.ru/ page (run by
the famous ENOG community member Phil Kulin). Detailed information
(also via API) is available at the https://reestr.rublacklist.net
run by RosKomSvoboda civil society group.
Kind regards,
Alexander Isavnin
Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum
----- End forwarded message -----
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
2:09 a.m.
On 4/19/18 1:57 PM, Brian Kantor wrote:
[This has been forwarded to a number of mailing lists,
but in
case you haven't already seen it, you may find it of interest.
This copy was received from the NANOG list. - Brian]
If anyone here is effected by this, please email me directly, AFIK our IPv4
space here is unaffected by this and I run a couple VPN servers.
Restricting information is the hallmark of every dictator from Castro to Putin.
The below was my reply on nanog.
On 4/19/18 1:36 PM, Sandra Murphy wrote:
> Russian ISPs MUST fully block all traffic to such
networks. The list is
> frequently updated and gets automatically propagated to ISP every once in a
> while, failure to block any address may result in 1500eur fine.
Per day? That's a cost of doing business. Can we donate to pay it somewhere?
> The
> infrastructure listed above is being added to the blocklist under
> “counter-terrorist and counter-extremist” order of the General Prosecutor
> Office, #27-31-2015/Id4082-15, issued in 2015 and often used for blocking
> an arbitrary unwanted content. The real reason for such blocking is an
> attempt to cut access to Telegram messenger, which refused to provide
> end-to-end encryption keys to the Federal Security Service (previously
> known as KGB).
Necessity is the plea for every infringement of human liberty.
It is the argument of tyrants; it is the creed of slaves.
-- William Pitt
--
Bryan Fields
727-409-1194 - Voice
http://bryanfields.net
2:12 a.m.
On 4/19/18 3:09 PM, Bryan Fields wrote:
If anyone here is effected by this
affected, sorry.
--
Bryan Fields
727-409-1194 - Voice
http://bryanfields.net
2:19 a.m.
On Apr 19, 2018, at 12:09 PM, Bryan Fields
<Bryan(a)bryanfields.net> wrote:
Restricting information is the hallmark of every dictator from Castro to Putin.
Please be careful bringing in political commentary into the mailing list for an
international hobby. While some may agree that your list of heads of state may fall under
the ‘dictator’ category, you may be offending members of our hobby. There are leaders in
the ‘free Western hemisphere’ doing similar things to communications networks too.
Ian VE7BST
2:24 a.m.
On 4/19/18 3:19 PM, Ian McLaughlin wrote:
you may be offending members of our hobby.
The delete key is right above the return on most Cyrillic keyboards.
--
Bryan Fields
727-409-1194 - Voice
http://bryanfields.net
2:27 a.m.
That would be backspace, not delete :p
</joking>
Ruben - ON3RVH
On 19 Apr 2018, at 21:25, Bryan Fields
<Bryan(a)bryanfields.net> wrote:
On 4/19/18 3:19 PM, Ian McLaughlin wrote:
you may be offending members of our hobby.
The delete key is right above the return on most Cyrillic keyboards.
--
Bryan Fields
727-409-1194 - Voice
http://bryanfields.net
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
2445
days inactive
2445
days old
6 comments
5 participants
participants (5)
-
Brian Kantor -
Bryan Fields -
Ian McLaughlin -
Jack Eifer -
Ruben ON3RVH