Box.com Encryption Errors

[Simplytoast]

Is seems using the .sz encryption the names of folders and files are generating illegal file names for Box.com. Is there a way to explained those banned characters?

https://developer.box.com/guides/api-ca ... on-errors/

[tobias]

Hello,
the encryption of file and folder names is unrelated to the Sz format.

Please post a snippet from the log file where I can see the exact encrypted name that Syncovery was trying to create on Box.

Older Syncovery versions may have tried to use the DEL character in some encrypted names, but recent versions no longer do that with Box.

[tobias]

OK I'm making a big test now and saw that some encrypted filenames start with ~$ and the Box connector in Syncovery rejects these names. Even though they are allowed on Box. I will fix that in the next update.

I would be grateful for any other specific examples of encrypted names that don't work.

[Simplytoast]

Absolutely, will do so tonight!

Thank you!

[tobias]

Hello,
the new versions 8.66 and 9.00rc1 should now both fix the problem.

In particular, they both allow filenames starting with ~$ on Box.

And on DropBox, where these filenames are really not allowed, the encryption algorithm will avoid such names.

If you find any other specific examples of filenames that don't work in encrypted form, please send them.

[Simplytoast]

I think the issue arrived as I am moving encrypted files (older) from Google to Box and Box is rejecting the files names.

I just need to do a fresh backup with encryption to resolve these issues

[tobias]

Hello,
yes, Syncovery sometimes uses different encryption characters for different clouds, unfortunately.

[Simplytoast]

That’s what I thought. No issues That’s why there are many backups!