Rclone encrypted config password bug and suggestions

Suspected Bug
1

Hi, I recently started using RcloneView v. 0.8.369 (Plus License) on Windows 10 and everything is generally working, thanks for your good work on this program!

However, I do have a problem to be able to access my encrypted rclone config (unencrypted works fine). First, when I type in the config password in the Config Password field in RcloneView’s General Settings, if I pause typing for just an instant the existing text is automatically highlighted and as I continue typing it replaces what was typed before. If I type the password really fast it would seem to be entered ok but there is no way to know if it was entered correctly because there is no option to show the password. After restarting rclone the UI says “Failed to load remote list”. As seen from another post I updated to version 0.8.423 and the behaviour is the same.

That is the only bug (?) that is preventing me from using an encrypted config file. The following are just suggestions, since I understand you are currently in active development, maybe you would like to implement them:

  1. You could allow for the equivalents of rclone’s alternate methods of supplying the config password. Namely, prompt for it on program start, using the RCLONE_CONFIG_PASS environment variable or reading it from standard input on program start. Those would be helpful.

  2. Another nice feature would be to be able to set a seperate password to lock the RcloneView UI on closing the window (or after a specified idle time). The program would remain running as usual with the taskbar icon still visible and would ask for the password when the UI is opened again. This would be an essential feature when sensitive data is stored on the remote volumes and whithout UI password protection anybody with access to the computer could access everything from all the connected remotes without any security restrictions.

Lastly, I saw another post saying that the rclone config password is stored in plain text. I don’t know where you are storing it, but it definitely should be encrypted. Is it now?

Thanks, let me know if you have any questions or comments…

1 Like
2

Hi, thanks for fixing the config password data entry bug, it is working correctly now (with the latest version).

The easiest to implement, and most secure method for handling the config password (IMHO) would probably be to prompt for it at the program startup. I don’t mind having to enter it when needed; I think that is preferable than leaving all my remotes open to whoever might gain access to my computer. The alternatives would also be nice to have, though. Thanks!

3 Likes
3

Thank you so much for your detailed feedback. It really helps us improve the app and prioritize important features.

Locking the app itself is now on our development list.

1 Like