Is rclone.conf needed to decrypt remotes?

Help and Support
22

I see, sorry for the confusion. I've tried this process and it still didn't work. Not sure what may be going wrong then.

23

post the entire config file, using rclone config show

redact all id/password/secret/token!

24 
[gdrive]
type = drive
client_id = XXX
client_secret = XXX
scope = drive
token = {"access_token":"XXX","token_type":"Bearer","refresh_token":"XXX","expiry":"XXX"}

that's the entire config, only one google drive with some encrypted folders

25

now create a crypt remote using rclone config

  • for the remote use gdrive:backups/wsl/node3
  • for the password(s), copy/paste the original password(s)`
  • for filename_encryption and directory_name_encryption, use the same settings as used when you set this up last year.

then test it with rclone ls remote:, just change the name remote: to whatever is the name of the crypt remote you created.

26

yeah, I tried it again, carefully following instructions but still the folder is empty. It doesn't mean that rclone did something wrong, I might have somehow changed the passwords without knowing it (strange). Thanks for trying anyway!

27

  • post the redacted config file

  • run this command and post the entire output, change remote: to the name of your crypt remote
    rclone lsd remote: -vv

28 
[crypt-node3]
type = crypt
remote = gdrive:backups/wsl/node3
filename_encryption = standard
directory_name_encryption = true
password = XXX
password2 = XXX

2021/08/14 14:40:00 DEBUG : rclone: Version "v1.53.3-DEV" starting with parameters ["rclone" "lsd" "crypt-node3:" "-vv"]
2021/08/14 14:40:00 DEBUG : Using config file from "/home/user1/.config/rclone/rclone.conf"
2021/08/14 14:40:00 DEBUG : Creating backend with remote "crypt-node3:"
2021/08/14 14:40:00 DEBUG : Creating backend with remote "gdrive:backups/wsl/node3"
2021/08/14 14:40:00 DEBUG : gdrive: Loaded invalid token from config file - ignoring
2021/08/14 14:40:00 DEBUG : Keeping previous permissions for config file: -rwxrwxrwx
2021/08/14 14:40:00 DEBUG : gdrive: Saved new token in config file
2021/08/14 14:40:00 DEBUG : Google drive root 'backups/wsl/node3': root_folder_id = "0AI4D1PVMexy3Uk9PVA" - save this in the config to speed up startup
2021/08/14 14:40:01 DEBUG : 6r5bm1fu4r9tfkn6kmsd0rrbdc: Skipping undecryptable dir name: Bad PKCS#7 padding - too long
2021/08/14 14:40:01 DEBUG : m1iskntob7jag9vf95ke8ilk1k: Skipping undecryptable dir name: Bad PKCS#7 padding - too long
2021/08/14 14:40:01 DEBUG : c5bp0a6og2sstckrvffdjdm07g: Skipping undecryptable dir name: Bad PKCS#7 padding - too long
2021/08/14 14:40:01 DEBUG : aco1i8ieh4ib1703re0vdpdqm8: Skipping undecryptable dir name: Bad PKCS#7 padding - too long
2021/08/14 14:40:01 DEBUG : 0vf0nks10skrj0f32r4bpat7io: Skipping undecryptable dir name: Bad PKCS#7 padding - too long
2021/08/14 14:40:01 DEBUG : q68hqfe2q5aau87sb9ia20mb6k: Skipping undecryptable dir name: Bad PKCS#7 padding - too long
2021/08/14 14:40:01 DEBUG : 2r6c604n38gka6tvlhqtru3okk: Skipping undecryptable dir name: Bad PKCS#7 padding - too long
2021/08/14 14:40:01 DEBUG : 9 go routines active
29

are you sure this is the correct location gdrive:backups/wsl/node3 for the crypted files.

can you post rclone lsd gdrive:backups/wsl/node3 -vv

30

yeah, added it to the comment above just now, the location seems to be okay, but it gives error on undecryptable dir name: Bad PKCS#7 padding - too long Thanks for mentioning -vv, it did shed some light on it.

31
  • you are using an old version of rclone, please update to latest stable v1.56.0
  • after that update, post rclone lsd gdrive:backups/wsl/node3 -vv
1 Like
32

thanks, will try that now

33 
2021/08/14 14:55:10 DEBUG : rclone: Version "v1.56.0" starting with parameters ["rclone" "lsd" "crypt-node3:" "-vv"]
2021/08/14 14:55:10 DEBUG : Creating backend with remote "crypt-node3:"
2021/08/14 14:55:10 DEBUG : Using config file from "/home/user1/.config/rclone/rclone.conf"
2021/08/14 14:55:10 DEBUG : Creating backend with remote "gdrive:backups/wsl/node3"
2021/08/14 14:55:10 DEBUG : Google drive root 'backups/wsl/node3': 'root_folder_id = 0AI4D1PVMexy3Uk9PVA' - save this in the config to speed up startup
2021/08/14 14:55:12 DEBUG : 6r5bm1fu4r9tfkn6kmsd0rrbdc: Skipping undecryptable dir name: Bad PKCS#7 padding - too long
2021/08/14 14:55:12 DEBUG : m1iskntob7jag9vf95ke8ilk1k: Skipping undecryptable dir name: Bad PKCS#7 padding - too long
2021/08/14 14:55:12 DEBUG : c5bp0a6og2sstckrvffdjdm07g: Skipping undecryptable dir name: Bad PKCS#7 padding - too long
2021/08/14 14:55:12 DEBUG : aco1i8ieh4ib1703re0vdpdqm8: Skipping undecryptable dir name: Bad PKCS#7 padding - too long
2021/08/14 14:55:12 DEBUG : 0vf0nks10skrj0f32r4bpat7io: Skipping undecryptable dir name: Bad PKCS#7 padding - too long
2021/08/14 14:55:12 DEBUG : q68hqfe2q5aau87sb9ia20mb6k: Skipping undecryptable dir name: Bad PKCS#7 padding - too long
2021/08/14 14:55:12 DEBUG : 2r6c604n38gka6tvlhqtru3okk: Skipping undecryptable dir name: Bad PKCS#7 padding - too long
2021/08/14 14:55:12 DEBUG : 4 go routines active

sadly, it appears to be the same

34

are you sure this is the correct location gdrive:backups/wsl/node3 for the crypted files.

can you post rclone lsd gdrive:backups/wsl/node3 -vv

35

90% sure that it is the right folder

2021/08/14 14:58:52 DEBUG : rclone: Version "v1.56.0" starting with parameters ["rclone" "lsd" "gdrive:backups/wsl/node3" "-vv"]
2021/08/14 14:58:52 DEBUG : Creating backend with remote "gdrive:backups/wsl/node3"
2021/08/14 14:58:52 DEBUG : Using config file from "/home/user1/.config/rclone/rclone.conf"
2021/08/14 14:58:52 DEBUG : Google drive root 'backups/wsl/node3': 'root_folder_id = 0AI4D1PVMexy3Uk9PVA' - save this in the config to speed up startup
          -1 2021-02-02 12:13:06        -1 0vf0nks10skrj0f32r4bpat7io
          -1 2021-02-02 12:13:02        -1 2r6c604n38gka6tvlhqtru3okk
          -1 2021-02-02 12:21:48        -1 6r5bm1fu4r9tfkn6kmsd0rrbdc
          -1 2021-02-02 12:15:01        -1 aco1i8ieh4ib1703re0vdpdqm8
          -1 2021-02-02 12:19:04        -1 c5bp0a6og2sstckrvffdjdm07g
          -1 2021-02-02 12:20:25        -1 m1iskntob7jag9vf95ke8ilk1k
          -1 2021-02-02 12:13:05        -1 q68hqfe2q5aau87sb9ia20mb6k
2021/08/14 14:58:53 DEBUG : 4 go routines active
36

yes, that looks correct.

about crypt-node3:, you need to use the EXACT same settings as you used when you first setup the crypted remote.
are you sure the passwords are the correct, original passwords?

37

80% sure the passwords are right, might still try to change settings, but clearly both directories and filenames are encrypted, so not sure if that will work

38

seems to me that the other settings look correct enough for rclone lsd crypt-node3: to work.
so if the passwords are correct, then it should work

39

thanks, in the end confirmation that passwords are at fault and not something silly is useful. With that out of the way dismantling the old drive from that laptop to retrieve the .rclone.conf file should be the way to go.

Thanks a lot for your help! That was interesting.

40

in the end, please update us...

41

sure, will do that