Skipping undecryptable dir name: bad PKCS#7

Help and Support
1

What is the problem you are having with rclone?

Cannot decrypt a crypt remote. I just tried re-creating the config for an encrypted rclone directory I have on an external SSD. However I get a bunch of errors after trying to use it, e.g. Skipping undecryptable dir name: bad PKCS#7. I'm not 100% sure I'm using the correct passphrases. Is that the issue though? If I can confirm that's the issue, I will try different passphrases. It's weird that googling that error message yields almost no results.

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

$ rclone version
rclone v1.71.2
- os/version: ubuntu 24.04 (64 bit)
- os/kernel: 6.14.0-35-generic (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.25.3
- go/linking: static
- go/tags: none

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

None. Using an external SSD.

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

rclone -vv ls crypt:/

Please run 'rclone config redacted' and share the full output. If you get command not found, please make sure to update rclone.

$ rclone config redacted
[crypt]
type = crypt
remote = /crypt
password = XXX
filename_encryption = standard
password2 = XXX
### Double check the config for sensitive info before posting publicly

A log from the command that you were trying to run with the -vv flag

$ rclone -vv ls crypt:/
2025/11/13 21:51:07 DEBUG : rclone: Version "v1.71.2" starting with parameters ["rclone" "-vv" "ls" "crypt:/"]
2025/11/13 21:51:07 DEBUG : Creating backend with remote "crypt:/"
2025/11/13 21:51:07 DEBUG : Using config file from "/home/redacted/.config/rclone/rclone.conf"
2025/11/13 21:51:07 DEBUG : Creating backend with remote "/media/redacted/datassd/crypt"
2025/11/13 21:51:08 NOTICE: 72xxxxxxmmhbsic5h6gs2r8: Skipping undecryptable dir name: bad PKCS#7 padding - too long
2025/11/13 21:51:08 NOTICE: di71xkieta8cexxxxtg114o: Skipping undecryptable dir name: bad PKCS#7 padding - too long
2025/11/13 21:51:08 NOTICE: 2nfnqxrulc36xxxsg8s3n2n0: Skipping undecryptable file name: bad PKCS#7 padding - too long
2025/11/13 21:51:08 NOTICE: 5mm1xxxxx5tl1iic7hcqhv0po: Skipping undecryptable file name: bad PKCS#7 padding - too long
2025/11/13 21:51:08 NOTICE: ntrcugkgoh1xxx50oqdu1k: Skipping undecryptable dir name: bad PKCS#7 padding - not all the same
2025/11/13 21:51:08 DEBUG : 4 go routines active
2

how did you do that? using rclone config, manually edit the config file or what?
what was the reason to re-create the config? corrupted config file, no backup or what?

does every single file file error out or just some specific files?

https://forum.rclone.org/search?q=%22PKCS%237%22

3

Yes recreated the config because no backup and created it with rclone config. Every single file errors out. I assume it's because I entered the wrong password1 or password2 but I'm not entirely sure.

4

this is very easy to re-create. change one character of the password

rclone lsd remote:
NOTICE: ospbtfl5arft08i545re73qjd0: Skipping undecryptable dir name: bad PKCS#7 padding - not all the same
NOTICE: hhjsbqu77lti8ddunq92fdosu0: Skipping undecryptable dir name: bad PKCS#7 padding - too long
NOTICE: a8b66hvf9pl7d1jfmo9sj0b4ns: Skipping undecryptable dir name: bad PKCS#7 padding - too long
NOTICE: no0t72436grdjpir4o2d8g1um4: Skipping undecryptable dir name: bad PKCS#7 padding - too long
NOTICE: u4arutgi5ht4nrrfgpm0qppbng: Skipping undecryptable file name: bad PKCS#7 padding - too long
5

I confirm that the issue was an incorrect passphrase.

6

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