SoylentNews is people
SoylentNews
The Russian parliament has approved a law creating a separate, domestic network, separate from the Internet. This Russian network of networks will be fully isolatable and will mean that the country's communications will become autonomous and able to continue functioning even when the plug is pulled on Russia's connections to the Internet at large. Concerns increase that this move will be used more for control of content and even just plain censorship, and make any attempts at circumventing restrictions much more difficult. The law is expected to take effect November 1st. Russia has already banned certain programs, such as Telegram.
One of the law's goals is to keep as much of the data exchanged between Russian internet users within the country's borders as possible. This aim may sound like a move to protect Russian users from external threats, but rights groups have warned that the new measures could ultimately be directed at Kremlin critics rather than international adversaries.
The idea of increasing the government's control over the internet is part of a more long-term national policy trend. In 2017, officials said they wanted 95% of internet traffic to be routed locally by 2020. Since 2016, a law has required social networks to store data about Russian users on servers within the country. The law was officially presented as an anti-terrorism measure — but many criticized it as an attempt to control online platforms that can be used to organize anti-government demonstrations.
Also at Silicon: Russian Parliament Passes Bill To Isolate Internet.
(Score: 0) by Anonymous Coward on Thursday April 18 2019, @01:35PM
I'm not sure it's all that hard. The "regular" internet will still exist in Russia. This is described as a separate network that is disconnected from the "regular" internet within the country. Anyone with access to both could create an interconnect using a computer with two interfaces. Using wifi for one interface you don't even have to be in physical contact with both networks.
As proof of concept, I have an example from a company I worked at previously. We had a "network outage" due to a security event, and our internal network was cut off from the general Internet. Of course we still had to get our jobs done during this "outage". We needed internal resources (wiki, source control, build tools, etc.) as well as external resources (api definitions, etc.). It was really easy to set up a Cellular based access point to the internet and connect wifi to that, and a physical ethernet connection to the internal network. many people did it using their phones... And did it before security realized they should tell everyone NOT to do that.
Separating any network from the Internet when both networks are available in near proximity is really difficult.