Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Manage FTP and SFTP protocol #2

Open
J-Jamet opened this issue Jan 21, 2022 · 3 comments
Open

Manage FTP and SFTP protocol #2

J-Jamet opened this issue Jan 21, 2022 · 3 comments
Labels
feature New feature or request

Comments

@J-Jamet
Copy link
Member

J-Jamet commented Jan 21, 2022

No description provided.

@Android-X13
Copy link

Android-X13 commented Mar 11, 2022

KeePassDX uses the connection capacity of your file manager. So we have to find or create file managers compatible with the SFTP protocol.

Material Files has SFTP support alhough it's still buggy. You can only create files but not edit or even view them. So trying to edit the remote database through KeePassDX when opening it via Material Files will fail. It won't show an error upon save, but the db will not be updated.

MiXplorer fails to update the db too, although it generally allows you to edit files successfully. I wouldn't use it though anyway because it's proprietary.

@J-Jamet
Copy link
Member Author

J-Jamet commented Mar 11, 2022

That's why we need to create an application that has a selectable cache and not impose it. If the file is updated from two places at the same time, I haven't seen any application (apart from Syncthing settings) that allows the user to select which conflicted file to share via the application's file provider.

@kraoli
Copy link

kraoli commented Mar 7, 2023

Maybe I understand the title wrongly. I think it would be better to not implement unencrypted protocols like ftp for security reasons.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants