Decrypted to encrypted name directory trees

What is the problem you are having with rclone?

I am not having a problem, just trying to understand features available for listing encrypted and decrypted names side by side. Ideally, I would like a listing similar to this or as full paths to files showing both the unencrypted and encrypted names/path.

Using the "rclone crypt" documentations examples, I'm looking to output something like:

├── file0.txt     hagjclgavj2mbiqm6u6cnjjqcg
├── file1.txt     v05749mltvv1tf4onltun46gls
└── subdir        86vhrsv86mpbtd3a0akjuqslj8
    ├── file2.txt         dlj7fkq4kdq72emafg7a7s41uo
    ├── file3.txt         8njh1sk437gttmep3p70g81aps
    └── subsubdir         7uu829995du6o42n32otfhjqp4
        └── file4.txt              b9pausrfansjth5ob3jkdqd4lc


file0.txt  --> hagjclgavj2mbiqm6u6cnjjqcg
file1.txt  --> v05749mltvv1tf4onltun46gls
subdir/file2.txt  --> 86vhrsv86mpbtd3a0akjuqslj8/dlj7fkq4kdq72emafg7a7s41uo
subdir/file3.txt  --> 86vhrsv86mpbtd3a0akjuqslj8/8njh1sk437gttmep3p70g81aps
subdir/subsubdir/file4.txt --> 86vhrsv86mpbtd3a0akjuqslj8/7uu829995du6o42n32otfhjqp4/b9pausrfansjth5ob3jkdqd4lc

Now as to my questions:

  1. Other than writing a script which walks a remotes directory tree and then uses "rclone cryptdecode --reverse" to provide the encrypted components of the path is there some easier way to generate what I am after?

  2. The "rclone cryptdecode" documentation also mentions "rclone backend decode". What are the merits of using one or the other of "rclone crypdecode" or "rclone backend decode"?

My motivation for this is that a fair amount of my workspace storage is used for storing items which do not need to be retrieved except in an exception circumstance, which would typically be discovered within a year. There might be a couple of hundred per year of which less than twenty might need to be retrieved. A significant portion of these are multi TB encrypted iso images.

I want to evaluate using Google Vault for archiving such items for a couple of years. My current understanding, possibly wrongly, is that such items would not count towards my quota. However, given the nature of Google Vault I could only retrieve such encrypted objects by using their original leaf node encrypted filenames. An additional enhancement would be to add a mechanism for making the encrypted leaf node names unique for the whole domain. I might do that manually, by adding a suffix to the encrypted names.

Any of your suggestions, thoughts, or insights will be welcomed?

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

> rclone version
rclone v1.64.2
- os/version: ubuntu 20.04 (64 bit)
- os/kernel: 5.4.0-166-generic (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.21.3
- go/linking: static
- go/tags: none

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

Google Workspace Enterprise Plus

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

remainder of template, not applicable.
I'm seeking suggestions

what about

rclone lsf -R --format=pe wasabi_en-calibre-crypt:zip
1 Like

Thanks. I was focusing on cryptdecode and didn't look at the "lsf" documentation in greater detail.

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