(I have this project in mind but I must already release a final version of KeePass DX.) It is also possible to create a file manager connected with plugins for each synchronization protocol. If your default file manager is not appropriate to your need, simply download one who do what you want. This is the purpose of a separate file manager application to do these actions (GDrive app, webdav app, or something else). Maintainability is also a big problem in this case, for each transfer protocol or integrated API, we must update the entire application and go through the validation workflow. It's worse with closed APIs because we do not know the inner code. This means that we have to be security experts for each of the integrated elements (potentially dangerous because connected to remote servers). If we start to integrate elements related to file sync by third party protocols, we will have to manage all the protocols and sync API in the main app. To share a text file with a team, we include the file in a shared folder, or we use another FTP service or the synchronization with another application. It's like LibreOffice, it does not connect to the internet. Recovering and sending files over the network has nothing to do with a password manager (In my opinion, let me explain). In software architecture, the software must be created to solve a single main problem. I do not prevent anyone from using non-free services, it's only a matter of trust, but I personally trust only the servers I have. I've been thinking of creating another file manager application for this proprietary cloud API but I have to previously finish KeePassDX. (Edit : The data merge has been done, the management of file conflicts will be done in the FileSync application) The application is still in beta and the synchronization must be created to retrieve the last partially updated data.GoogleDrive is integrated with the default file manager and works (in part, even if it has caching and synchronization problems). If OneDrive and DropBox have not correctly created their applications to be compatible with the file manager and URI links of the device, it's not the fault of KeePassDX.
The phone's file manager should be the only one to access files (even remote)
If I start to integrate connection code directly in the application, it will integrate all the APIs of all existing clouds to not favor one more than another (can do a lot of problems).Google Drive, OneDrive and Dropbox are not free software, and KeePassDX wants to stay under GPLv3 license.There are several reasons why cloud code is not directly integrated into KeePassDX :
0 kommentar(er)
