Solved: How to have binary identical files from different crypt remotes?

Help and Support
1

What is the problem you are having with rclone?

different crypt remotes set up with the exact same passwords can read (decrypt) each others files but produce totally different files (same name, date, size but different content) when encrypting.

How to have binary identical files from different crypt remotes?

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

rclone v1.66.0

  • os/version: Microsoft Windows 10 Pro 22H2 (64 bit)
  • os/kernel: 10.0.19045.3031 (x86_64)
  • os/type: windows
  • os/arch: amd64
  • go/version: go1.22.1
  • go/linking: static
  • go/tags: cmount

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

local disk

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

rclone sync C:\Test\cleartext crypttest1:
rclone sync C:\Test\cleartext crypttest2:

Then I do compare encrypted folders

Please run 'rclone config redacted' and share the full output. If you get

[crypttest1]
type = crypt
remote = C:\Test\crypttext1
password = XXX
password2 = XXX

[crypttest2]
type = crypt
remote = C:\Test\crypttext2
password = XXX
password2 = XXX

2
21731×368 242 KB

2

Short answer - no as that defeats encryption if they are identical.

3

What parts of the config (besides the passwords) determines the binary outcome of the encryption?

4

It's explained here:

1 Like
5

What is happening here as per docs:

Encryption uses cryptographic salt, to permute the encryption key so that the same string may be encrypted in different ways.

It is essential to make life of potential hacker much more difficult.

You can read more simple theory here:

rclone does follow good practices here - it would be worrying if it was not. When it comes to crypto it is the best approach. Trying to reinvent the wheel usually leads to disasters in this space.

6

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