Can Rclone Encrypt Config File Using Rc

What is the problem you are having with rclone?

Im trying to create a rclone config through rc api call( and in turn create a mount ( using the remote configured in config.

  1. Is there a way to encrypt the config file while using Rc similar to "set configuration password" in interactive mode ?
  2. If the password can be set, how to pass it in the body of the mount api call ?

Run the command 'rclone version' and share the full output of the command.

rclone v1.61.1

  • os/version: Microsoft Windows 10 Enterprise 21H2 (64 bit)
  • os/kernel: 10.0.19044.2486 (x86_64)
  • os/type: windows
  • os/arch: amd64
  • go/version: go1.19.4
  • go/linking: static
  • go/tags: cmount

Which cloud storage system are you using? (eg Google Drive)


The command you were trying to run (eg rclone copy /tmp remote:tmp)

The rclone config contents with secrets removed.

A log from the command with the -vv flag

Paste  log here

I don't think this is possible at the moment. If you want an encrypted config file, you'd start rclone with an encrypted config file or use one of the methods outlined here to give rclone the password

@ncw :
Thanks for the reply.
My idea is to use only rc api's to setup config and mount.
I'm able to create config using rc, but not sure how to encrypt the .conf file using rc.

I don't think you can at the moment - want to add some API to do that?

That will be helpfull.
Just wanted to further know what will /config/password do ? This api is setting password in the .conf file. But mount api is not prompting for this password ?

No API sets or asks for the config password at the moment.

For the time being you need to set up rclone with the api password when you run it (eg as parameters to rclone rcd).

Thanks for the info.
Need a suggestion on what would be the best way to ask for access & secret keys from end users in a production setup while mounting on S3 ( mount will be done using customers aws account).

You'd probably ask the customers for access and keys which were limited to a single bucket. You can make these in the AWS console. Is that what you mean?

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.