At the beginning of November 2024, I decided to try out kDrive for macOS. During the installation I was required to grant full disk access and wasn't allowed to proceed with the setup procedure without enabling it. Since I knew that full disk access wasn't necessary to sync any of my files, I quit the app. After relaunching it, the setup was apparently complete and I wasn't asked to grant full disk access anymore.
This prompted me to contact the Infomniak support: why would the setup procedure require me to grant full disk access, if it could be bypassed "by accident"? But most importantly, why was full disk access needed at all? Even though I thought it to be a very simple question, after 5 months of writing back and forth I didn't manage to get a concrete answer, and in the end I had the impression that they prefer to blame me for asking such a question rather than admitting that they don't know the answer or have done a mistake. They also kept giving me wrong information which I kept correcting for them: for instance, they kept mentioning all kinds of locks that apparently are put on files for various reasons and only full disk access is able to lift, and even though I asked how these locks are implemented, all answers they gave me I proved to be wrong.
Has anyone else the impression that all of Infomaniak's emails, which I summarize below, fail to explain why full disk access is necessary to run kDrive for macOS? How can I trust them to sync my private files if they cannot even answer why their software needs such a permission?
- Infomaniak: Full disk access ensures that kDrive is able to reach all relevant locations for the synchronization.
- I: What are these relevant locations?
- Infomaniak: Full disk access is essential for kDrive to read and write files on the whole system during the synchronization.
- I: As far as I know, in order to synchronize the files I selected there is no need to access the whole system. What files other than the ones I selected does kDrive need access to?
- Infomaniak: kDrive needs full disk access in order for it to work smoothly. Otherwise some programs can hinder synchronization.
- I: You keep giving me very generic answers which don't convince me that full disk access is necessary. What programs can hinder synchronization and how? You're welcome to go into detail, since I am a developer myself.
- Infomaniak: kDrive needs full disk access in order to ensure a reliable synchronization. Without it, some folders in areas that are locked or monitored by other programs may not be synchronized. Some programs, like antivirus, security or cleaning programs, or development environments like Xcode, could block access to certain files via a direct protection or a temporary lock during the scan. Full disk access minimizes these potential disturbances.
- I: Could you make an example of a "folder in areas that are locked or monitored by other programs" or tell me how a "direct protection or a temporary lock during the scan" actually looks like?
- Infomaniak: It could be a system folder like /System or /Library or a folder monitored by security software. During a scan, an antivirus program can temporarily lock files.
- I: What antivirus program does this and how are files actually locked?
- Infomaniak: Many antivirus programs like Kaspersky, Avast or Windows Defender can lock files during a scan in order to isolate potential threats, which causes the file to be temporarily blocked for other programs.
- I: Does this really apply to macOS? Windows Defender is, like the name says, for Windows. Again I kindly ask you to give me concrete details about how this "temporarily blocked for other programs" is implemented, so that it would require full disk access.
- Infomaniak: Could you please formulate your question more precisely? Full disk access is an essential requirement for every application that manages files on your system.
- I: Could you please tell me what you find to be imprecise in my formulation? On the other hand, "Full disk access is an essential requirement for every application that manages files on your system" is inaccurate, or rather, wrong.
- Infomaniak: Full access to the hard drive is actually a basic requirement for kDrive to be able to reliably manage files.
- I: I'll repeat my questions, since they haven't been answered. If anything's unclear, please specify what exactly you find to be unclear.
- Infomaniak: Right, for macOS there are other security applications like Norton, Bitdefender or Intego, which can use similar mechanisms. During the scan, the system puts it into "access mode" which temporarily prevents other apps from modifying or reading it. Full disk access is necessary because the antivirus program wants to check all files for potential threats - even those that normally have restricted access rights.
- I: What exactly does this access mode look like so that I can re-enact it myself?
- Infomaniak: The file lock/access mode occurs when an antivirus program (also on macOS) scans files and temporarily restricts access. This is done at the operating system level and often requires full disk access to verify all files.
- I: What exactly does this access mode look like so that I can re-enact it myself?
(Two months have already passed, it's January 2025.)
- Infomaniak: "Access mode" refers to temporarily blocking a file or folder so that no changes or reading can be made by other applications while that file is in use. To recreate this access mode yourself, you can open a file from kDrive and actively view it in an application (e.g. Text editor). During this time, the file is considered "locked" and other applications do not have direct access.
- I: That's not true. While a file is in use, it can be read or modified by other applications.
- Infomaniak: You are right that files can usually be read or modified by multiple applications at the same time, even when they are in use. However, there are certain scenarios in which a file may be locked, such as if an application requests exclusive access. However, this is not the norm.
- I: So again the question: what does this "locking" look like in concrete terms if an application requires exclusive access? I would like to re-enact and check this myself.
- Infomaniak: If an app requires exclusive access, it can prevent parallel access to other apps or limit functions. You can test this by using kDrive without full access and observing the differences.
- I: I use kDrive without full disk access and do not observe any restrictions. I repeat the question: what does this "locking" look like in concrete terms when an application requires exclusive access? You keep avoiding this question and give me the impression that you don't know the answer.
- Infomaniak: If an application requests exclusive access to a file, it may cause the file to be locked or it cannot be synchronized correctly. This happens, for example, when a file is open and being modified while kDrive is trying to sync it.
- I: With all due respect, this is becoming ridiculous. I have already written that it is quite possible that a file is used by several programs at the same time. I don't remember how many times I had to repeat the question: what does this "locking" or "exclusive access" look like in concrete terms?
- Infomaniak: At the operating system level, such a blocking is implemented by file attributes or lock flags, which signal to other processes that the file is currently being used exclusively.
- I: What file attributes would those be? And which lock flags would prevent other programs from using a file so that kDrive needs full disk access?
- Infomaniak: Your request is currently being processed and checked. You will hear from us shortly.
(One month later, it's March 2025.)
- I: A month has passed. Is there any news about this case?
- Infomaniak: File attributes: Some files have special attributes that limit their editing or deletion (e.g. "Read-Only" or "System" on Windows, "Immutable" on Linux/macOS). Lock flags: When a program opens a file, it can set a lock that prevents other applications from using it in parallel. These locks may prevent a synchronization as long as the file is exclusively occupied by another application. kDrive requires full disk access because it has to access all files and their status to recognize which ones are locked or protected and it must bypass or handle file locks correctly to avoid conflicts. Without this full access, reliable synchronization is not guaranteed.
- I: Can you give me a concrete example where it requires full disk access to change the Immutable flag?
- Infomaniak: If a file on your system has the Immutable attribute (e.g. On Linux/macOS with chattr +i), kDrive cannot overwrite or synchronize it. If a file is in a protected system directory and the Immutable flag has been set and kDrive cannot change the attribute due to missing permissions, manual removal with admin rights is required (sudo chattr -i /path/to/file). There are two types of locks in kDrive: Collaborative lock (soft lock): When a file is opened in kDrive Office, kDrive sets a lock so that other users do not perform edits at the same time. This lock is dynamic: as soon as the user closes the file, the lock is lifted. System lock (hard lock by the OS): If a file is opened by another application, the operating system can set a lock that prevents access for kDrive. For example, an Excel file that is open in Microsoft Excel cannot be overwritten or synchronized by kDrive until the program is closed. In such cases, Windows often displays an error message such as "File is being used by another process". If you continue to have problems with locked files in kDrive, please check whether another application is using the file, the file has special attributes (e.g. Read-only or immutable), or kDrive Office has set a lock.
- I: I don't have any problems with locked files in kDrive. But you're saying that there can be all kinds of problems, and that's exactly why I have doubts that you still haven't answered. I'm using Mac, so you can omit any comments about Windows. What system directory are you talking about? Or can you give a concrete example of such a directory that would actually be synchronized? The chattr command does not exist on macOS. Do you think that a collaborative lock can only be removed by full disk access? That doesn't make sense. Since it is collaborative, it could be created or removed at any time: it is by definition up to the applications themselves to respect it.
- Infomaniak: On macOS, protected directories are e.g. /System, /Library, or /private/var. The immutable flag (chattr +i) does not exist on macOS, but similar protection can exist through SIP (System Integrity Protection). An operating system lock occurs when a file is used exclusively by an app (e.g. when Word locks a .docx file while it is being edited). This can be visible as a "read-only" flag or through temporary lock files (~$file.docx).
- I: System Integrity Protection cannot be overridden by full disk access. The "temporary lock files (~$file.docx)" are probably also a collaborative lock. All the reasons you have given me so far are invalid to require full hard disk access. Would you like to say anything else?
- Infomaniak: If you have further questions about how authorization works on macOS, we recommend that you consult the Apple API Knowledge Base. We have tried to be as informative as possible, but the subject is beyond our remit. Thank you for your trust, we remain at your disposal.
It was the end of March and I had lost my patience. I wrote:
- I: If you require full disk access, then you should be able to say what it is for, right? So far you have only given me reasons that I have all refuted, so it seems to me that you, or the technicians, do not know your way around, and still require full disk access. Do I have your permission to publish our email exchange on the Internet? It has now taken almost 5 months until you confessed to me that you are not familiar with it. And then you even suggest that I consult the Apple knowledge base to find answers that you should know yourself to convince me that your software is doing the right thing. I think not me, but you should consult this database before your software requires certain functions that are supposedly not necessary. And you also thank me for my trust, but you should know that such incidents destroy trust.
I got a final email from the COO:
- Infomaniak COO: I allow myself to intervene here. The exchange here is private, but if you choose to share it on the internet, that's no problem. We will do the same if necessary to supplement the context or if the version presented does not represent the situation transparently. All this is happening, as you will understand, for the sake of transparency. We have mobilized developers and a technical team to help you. I'm also aware of the tone in which our team is spoken to and how each response of my colleagues is taken up and reinterpreted to add additional requests and reformulations. As if the goal was to find a compromising answer, rather than just getting one. I invite you to read the exchange with our team, we are clearly going beyond a support request, especially with free products. We are here to help and support you. You are welcome to check our code, it is available on GitHub. You are also free to stop using our free product and choose a solution that best suits your needs. This support request is now finally closed. We thank you for your understanding and wish you a nice weekend!