BUG: ChangeNotify was unable to decrypt

What is the problem you are having with rclone?

ChangeNotify was unable to decrypt ... is showing up for files and folder that are not within the scope of the remote that is mounted - for example the unencrypted name of the root folder, or it's parallel folders which also have unencrypted names.

What is your rclone version (output from rclone version)

rclone v1.49.4-003-gb5ea6af6-v1.49-fixes-beta

  • os/arch: windows/amd64
  • go version: go1.12.10

(Still testing this fix build for NCW on another issue, but I don't think it's relevant to this error)

Which OS you are using and how many bits (eg Windows 7, 64 bit)

Win10-64

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

Google Drive

So I have an encrypted remote mounted in "C1test" (unencrpyted name) at the root of the drive. It's giving me these errors (among loads more):

2019/10/04 04:16:08 NOTICE: Encrypted drive 'TD2SA2C:': ChangeNotify was unable to decrypt "Crypt1": illegal base32 data at input byte 2
2019/10/04 04:16:10 NOTICE: Encrypted drive 'TD1SA1C:': ChangeNotify was unable to decrypt "Crypt1": illegal base32 data at input byte 2
2019/10/04 04:16:12 NOTICE: Encrypted drive 'TD1SA2C:': ChangeNotify was unable to decrypt "Crypt1": illegal base32 data at input byte 2
2019/10/04 04:16:12 NOTICE: Encrypted drive 'TD3SA1C:': ChangeNotify was unable to decrypt "Crypt1": illegal base32 data at input byte 2
2019/10/04 04:16:16 NOTICE: Encrypted drive 'TD3SA2C:': ChangeNotify was unable to decrypt "Crypt1": illegal base32 data at input byte 2
2019/10/04 04:17:34 NOTICE: Encrypted drive 'TD2SA1C:': ChangeNotify was unable to decrypt "EMPTYTEST": illegal base32 data at input byte 4
2019/10/04 04:17:44 NOTICE: Encrypted drive 'TD2SA1C:': ChangeNotify was unable to decrypt "C1": not a multiple of blocksize
2019/10/04 04:17:45 NOTICE: Encrypted drive 'TD2SA2C:': ChangeNotify was unable to decrypt "EMPTYTEST": illegal base32 data at input byte 4
2019/10/04 04:17:53 NOTICE: Encrypted drive 'TD1SA1C:': ChangeNotify was unable to decrypt "BF3": illegal base32 data at input byte 3
2019/10/04 04:17:53 NOTICE: Encrypted drive 'TD1SA1C:': ChangeNotify was unable to decrypt "DXtory capture": illegal base32 data at input byte 1
2019/10/04 04:17:53 NOTICE: Encrypted drive 'TD1SA1C:': ChangeNotify was unable to decrypt "EMPTYTEST": illegal base32 data at input byte 4
2019/10/04 04:17:54 NOTICE: Encrypted drive 'TD2SA2C:': ChangeNotify was unable to decrypt "C1": not a multiple of blocksize

The only problem is - none of these folders are inside the scope of the remote - they are parallel to it.

The scope is currently limited in the path of the crypt-remote and not the "root-folder" setting of the Gdrive remote. I don't know if this has anything to do with it - but it seems like it should not care about polling updates outside of it's scope regardless (or just not request them to begin with if possible).

The issue seems very much similar to this:


But I don't know if that ever went anywhere...

I think that probably needs to be turned into an issue!

Those NOTICE messages should be harmless if annoying.

Yes I figure they won't do any harm since not being able to decrypt data I will never access on that remote anyway seems not a big threat. It's just annoying (and probably confusing to less technical users) + I am slightly worried that it would be jamming up the polling system and delaying things with a large amount of retries or something... but I have no proof of that actually happening currently.

I will make an issue for it.

1 Like

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