{"id":2815,"date":"2019-06-04T15:21:42","date_gmt":"2019-06-04T15:21:42","guid":{"rendered":"https:\/\/www.dekuzu.com\/en\/?p=2815"},"modified":"2020-02-18T16:36:30","modified_gmt":"2020-02-18T16:36:30","slug":"russian-google-yandex-can-go-the-telegrams-way-in-russia","status":"publish","type":"post","link":"https:\/\/www.dekuzu.com\/en\/2019\/06\/russian-google-yandex-can-go-the-telegrams-way-in-russia.html","title":{"rendered":"Russian Google Yandex can go the Telegram\u2019s way in Russia"},"content":{"rendered":"\n

As almost everybody knows the access to Telegram messenger services is to be restricted in Russia under court order. Despite the blocking the Telegram is functioning in Russia and the administration of Russian president has even announced a tender to monitoring popular Telegram channels. But Yandex can\u2019t be so brave and strong like Telegram because it could lose its business in Russia, in other words it could be destroyed and the Russian internal market could be absolutely free for Google.<\/span><\/p>\n

<\/span><\/p>\n

According to Russian media RBC<\/a> Yandex has been required to provide Russian Federal Security Service (FSB) with encryption keys, but Yandex doesn\u2019t want to do this and plays for time. These keys could provide FSB with access to all information on Yandex\u2019s users and Yandex could lose its users because the last don\u2019t want to share their personal information with anyone. According to news few months ago FSB required Yandex to provide encryption keys in order to decrypt user\u2019s data for two Yandex\u2019s services \u2013 Yandex.Mail and Yandex.Disk.<\/span><\/p>\n

Yandex.Mail provides its users with electronic mailing services and Yandex.Disk provides its users with opportunity to store and share their digital files, like Google Disk. Yandex did not provide FSB with encryption keys, but it should do this within 10 days following the requirement. When FSB did not receive encryption keys from Telegram the court ordered to restrict access in Russia to it. The two services in question are \u201corganisers of information dissemination\u201d therefore Yandex has to provide encryption keys under Yarovaya law if FSB requires so.<\/span><\/p>\n

Yandex believes FSB interprets Yarovaya law very broadly. The FSB requires Yandex to provide it with session encryption keys. Such keys could provide FSB with access to electronic messages of users and analyse all users\u2019 traffic. This may mean that FSB can receive access to all Yandex services in the context of users\u2019 data and traffic. Yandex concerns that providing FSB with encryption keys could make its users leave Yandex services. The fewer users the less market shares because Google is not forced to provide FSB with encryption keys.<\/span><\/p>\n

If Yandex does not provide FSB with encryption keys within fixed term it can be held liable under administrative code and face fine up to 1 mln Roubles. If after that Yandex still fails to satisfy FSB requirement within 15 days Russian internet watchdog Roskomnadzor can require the court to block in Russia those Yandex services for which the required encryption keys have been not provided. The Telegram has been blocked in Russia the same way. Industry stakeholders don\u2019t believe Yandex will be blocked in Russia, they believe Yandex and FSB would reach a compromise.<\/span><\/p>\n

Yandex has stated that compliance with Yarovaya law does not necessary breach users\u2019 privacy. Yandex believes \u201cit is very important to balance between users\u2019 security and privacy and taking into account the principles of equial regulation for all market players\u201d.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

Yandex has been required to provide Russian Federal Security Service (FSB) with encryption keys, but Yandex doesn\u2019t want to do this<\/p>\n

Continue readingRussian Google Yandex can go the Telegram\u2019s way in Russia<\/span><\/a><\/div>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[18,14,29,7,4,39,32,24],"tags":[],"class_list":["post-2815","post","type-post","status-publish","format-standard","hentry","category-law","category-competition","category-digital","category-enforcement","category-internet","category-interpretation","category-russian-law","category-telecom","entry"],"_links":{"self":[{"href":"https:\/\/www.dekuzu.com\/en\/wp-json\/wp\/v2\/posts\/2815","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dekuzu.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dekuzu.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dekuzu.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dekuzu.com\/en\/wp-json\/wp\/v2\/comments?post=2815"}],"version-history":[{"count":1,"href":"https:\/\/www.dekuzu.com\/en\/wp-json\/wp\/v2\/posts\/2815\/revisions"}],"predecessor-version":[{"id":2816,"href":"https:\/\/www.dekuzu.com\/en\/wp-json\/wp\/v2\/posts\/2815\/revisions\/2816"}],"wp:attachment":[{"href":"https:\/\/www.dekuzu.com\/en\/wp-json\/wp\/v2\/media?parent=2815"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dekuzu.com\/en\/wp-json\/wp\/v2\/categories?post=2815"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dekuzu.com\/en\/wp-json\/wp\/v2\/tags?post=2815"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}