Encrypt unencrypted Dropbox

Help and Support
1

What is the problem you are having with rclone?

I moved my files from GDrive to Dropbox but need to get them encrytpted.

I understand that I need to mount the the crypt and dropbox in Rclone, but I then don't know how to move the files from unencrypted to encrypted, I can't seem to find any guides on this anywhere.

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

1.63.0

Are you on the latest version of rclone? You can validate by checking the version listed here: Rclone downloads
Yes

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

Dropbox

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

Unsure what commands I need to run

The rclone config contents with secrets removed.

Don't currently have one yet

2

welcome to the forum,

the encryption is done on-the-fly.
as rclone copies a file into a crypt remote, rclone will crypt the file
as rclone copies a file from a crypt remote, rclone will decrypt the file.

rclone mount is not required but can be used.

here is an example from https://raw.githubusercontent.com/animosity22/homescripts/master/rclone.conf

[DB]
type = dropbox
client_id = <CLIENTID>
client_secret = <CLIENTSECRET>
token = {"access_token":"TOKEN","token_type":"bearer","refresh_token":"REFRESH","expiry":"2022-01-17T16:00:01.80374356-05:00"}

[dbcrypt]
type = crypt
remote = DB:media
filename_encryption = standard
password = <PASSWORD>
password2 = <PASSWORD>
directory_name_encryption = true

let's assume the files to be crypted files are stored at DB:folder
rclone copy DB:folder dbcrypt: --dry-run -vv

3

Hi,

Thanks for replying, I have both mounted and tried the dry run with some test files and it seems to error:

rclone copy dropbox:Test Crypt: --dry-run -vv
2023/07/14 00:40:05 DEBUG : rclone: Version "v1.63.0" starting with parameters ["rclone" "copy" "dropbox:Test" "Crypt:" "--dry-run" "-vv"]
2023/07/14 00:40:05 DEBUG : Creating backend with remote "dropbox:Test"
2023/07/14 00:40:05 DEBUG : Using config file from "/home/ubuntu/.config/rclone/rclone.conf"
2023/07/14 00:40:05 DEBUG : Creating backend with remote "Crypt:"
2023/07/14 00:40:05 Failed to create file system for "Crypt:": didn't find section in config file

The config file Rclone created was:

[dropbox]
type = dropbox
token = {"access_token":"<>","token_type":"bearer","expiry":"0001-01-01T00:00:00Z"}

[crypt]
type = crypt
remote = dropbox:Crypt
password =<>
password2 = <>

4

the remote name you created is crypt, but command uses Crypt

so either change the name of the remote or the command.

5

Spotted that just as you were replying :smile:

Dry run seemed to work perfectly:

Transferred: 270.117 GiB / 270.117 GiB, 100%, 0 B/s, ETA -
Transferred: 160 / 160, 100%
Elapsed time: 1.7s

2023/07/14 00:44:48 DEBUG : 10 go routines active
2023/07/14 00:44:48 INFO : Dropbox root 'Test': Committing uploads - please wait...
2023/07/14 00:44:48 INFO : Dropbox root 'Crypt': Committing uploads - please wait...

6

you really should create your own dropbox app and use the client id from that.

7

This was just a VPS I got to move my files from GDrive to Dropbox

On my box hosting Plex etc it's connected using a dropbox app instead.

Someone mentioned adding flag filename_encoding = base32768 to stop issues with long file names. Where would this be added?

8

config file, as much discussed in the forum and docs.

9

Thank you

Just moving some files over and if I check the crypt it has some numbers at the start of files that are encrypted:

jason1984@zion:~/.config/rclone$ rclone ls crypt:
1620943519 FILENAME
1621533370 FILENAME
1639140714 FILENAME
3647306271 FILENAME

Is this correct?

10

these numbers are files sizes in bytes.

Encrypted things are in dropbox:Crypt folder - when you use crypt: remote it transparently encrypt/decrypt everything on the fly.

11

that is ok, that is the size of file in bytes.

to remove the file size from the listing,
rclone lsf --format=p

1 Like
12

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