prehistory
Hey Habr!
A rather strange error led me to write this post, which I received last night on a laptop with Linux (yes, I'm one of those strange people who use GNU / Linux on a laptop) instead of the contents of my Yandex.Disk:
$ ls -l /mnt/yadisk
ls: reading directory '.': Input/output error
total 0First thought: the network has fallen off, it's okay. But when trying to remount the directory, a new error appeared:
$ sudo umount /mnt/yadisk && rclone mount --timeout 30m ya:/ /mnt/yadisk
2020/02/21 20:54:26 ERROR : /: Dir.Stat error: [401 - UnauthorizedError] Unauthorized (ΠΠ΅ Π°Π²ΡΠΎΡΠΈΠ·ΠΎΠ²Π°Π½.)It was already weird. Is the token rotten? It doesn't matter, I'll authorize again!
$ rclone config
... (ΠΎΠΏΡΡΡ ΡΡΡ Π²Π΅ΡΡ Π²ΡΠ²ΠΎΠ΄ ΡΠ΅ΡΠΌΠΈΠ½Π°Π»Π°) ..After going to the web and trying to log in there, I get a more specific message:
This application has been blocked for malicious activity, therefore access is not allowed (unauthorized_client).
First thought: what?
About rclone
A little help:
- well known utility for working with cloud storage (repeatedly , , mentioned on HabrΓ©). The author calls it "rsync for cloud storage", which is quite capacious. But the functionality is not limited to this: in addition to the rsync functions, it can also mount disks, perform the ncdu function (which, by the way, once allowed me to detect an incorrect calculation of free space on Yandex.Disk and successfully solve this problem through technical support), as well as a bunch of other things. The utility supports both dozens of cloud storages and more traditional protocols - WebDAV, FTP, rsync and others. To access Yandex.Disk, the utility uses Disk.
The utility is truly unique and (in my opinion) is the class of programs that you install once, and they bring benefits all the time.
What happened?
Turning to Google, I immediately realized that I was not alone. Eat , as well as a discussion on .
Brief content: the client_id of the utility is blocked by Yandex.Disk, which is why it is no longer possible to log in. You can try to change the client_id, but not the fact that the same fate will not befall the new id.
Support answer :
The fact is that the Rclone program allows you to use Yandex.Disk as an infrastructure component, while Yandex.Disk is a personal service that is not designed to solve such problems. Therefore, we do not support the operation of the Rclone-Yandex.Disk bundle.
"Infrastructural Component"? Well, if itβs impossible, then itβs probably described in the rules, I thought, and nothing like that in or his I did not find.
Okay, let's write to support.
The first answer arrives 1 to 1 the one that is published above (about the "infrastructure component"). Okay, we're not proud.
Further correspondence with support
I am:
Can you please tell me which service rule is violated?
I studied the terms of use of Yandex disk and there are no prohibitions on using "as an infrastructure component".Moreover, I cannot use the utility from my personal laptop to work with the disk. This does not fall under the "infrastructure component" at all. The regular disk client is terrible, sorry.
Support:
Sergey, the fact is that Yandex.Disk is primarily a personal service that is not designed to automatically download backups.
You can synchronize data between your computer and Yandex.Disk, and use the Yandex.Disk web interface to upload files and work with them.If for some reason you are not satisfied with our program, please let us know. Traditionally, we listen to the opinions of users when releasing product updates.
You can familiarize yourself with the documents regulating the use of the service, in particular, the "Yandex Services User Agreement" published at: , as well as the "Terms of Use of the Yandex.Disk Service":
To solve tasks that require a lot of power, we recommend using Yandex.Cloud. This is another Yandex cloud service created to solve business problems. You can learn more about Yandex.Cloud here:
I am:
You did not answer my question. Please tell me which point of the service rules violates the use of rclone? I carefully studied the rules on your link (even before you sent them).
Most recently, you wrote a post that Yandex strongly supports OpenSource and without OpenSource, Yandex and the modern Internet would not exist ().
And now you're blocking the OpenSource utility for a bogus reason.
By the way, the program does not "download backups in automatic mode", the program is designed to work with cloud storage, including synchronizing data between a computer and Yandex.Disk. And this is my main use-case of the utility, which is now unavailable.
Support:
According to clause 3.1. of the "User Agreement" Yandex has the right to establish restrictions on the use of services for all Users, or for certain categories of Users (depending on the User's location, the language in which the service is provided, etc.), including: the presence / absence of certain functions service, the period of storage of mail messages in the Yandex.Mail service, any other content, the maximum number of messages that can be sent or received by one registered user, the maximum size of a mail message or disk space, the maximum number of requests to the service for a specified period of time, the maximum period content storage, special options for downloadable content, etc. Yandex may prohibit automatic access to its services, as well as stop accepting any automatically generated information (for example, email spam).
The user is also warned about this in clause 4.6. "Terms of Use for Yandex.Disk".
Please note that the "Yandex.Disk Terms of Use" also establishes the obligation for the User to act in good faith and refrain from abusing the functions of the Service. The User, among other things, undertakes to refrain from organizing mass file sharing using the functions of the Service.
Yandex has the right to apply rules, limits and restrictions aimed at preventing, restricting and suppressing mass file sharing in accordance with the rules of clause 4.5. of these Terms.
The last answer brought clarity. Especially, the first two paragraphs with reference to clause 3.1. "User Agreement" Yandex and clause 4.6. "Terms of Use for Yandex.Disk". The text of 4.6 is not given here, I will give it:
4.6. Yandex reserves the right to establish any rules, limits and restrictions (technical, legal, organizational or otherwise) on the use of the Service, and may change them at its sole discretion, without prior notice to the User. In cases where it is not prohibited by law, these rules, limits and restrictions may be different for different categories of Users.
Conclusions?
Most recently, respected in its wrote that Yandex believes that:
We at Yandex believe that the modern Internet is impossible without an open source culture and people who invest their time in the development of open source programs.
But in practice it turns out quite differently. An excellent utility is blocked for something that is not prohibited by the rules of the service. For the fact that the utility allows you to use open public The Disk API's intended purpose is to upload files. They block not for violating the rules of the service, but because they can.
It is doubly strange that it is not specific violators of the rules that are blocked (it is also unclear which ones, the use of a disk for backups is not prohibited anywhere in the rules). A tool is blocked, the backup function of which is only one of many.
What is an infrastructure component and why they cannot be used with a disk is also not clear. Even the browser can be used as an "infrastructural component", shouldn't it be forbidden to use the disk in the browser?
What to do?
For now, use your client_id and move on. But, judging by the response from technical support, we can expect the witch hunt to continue and also block other client_id, user-agent rclone, or even some heuristic ways to block the utility.
PS I sincerely hope that there was a simple mistake or misunderstanding. Excellent specialists work in Yandex (many of whom I know personally) and among them, I am sure, there are rclone users.
Update 24.02.2020:
Π podcast of Radio-T, whose co-host is also a respected Bobuk, the blocking of rclone was discussed. .
Source: habr.com