Encrypted rclone Copies to a Storage Box with Pikkumies
Copy a folder from your own Linux machine to a Pulsed Media Storage Box so that the box cannot read the contents or the names of your files, then let Pikkumies run the copy and list the result from one plain request. In the test run shown below, one sentence copied a small Documents folder (3 files, 293 KiB) through an rclone crypt remote and checked that every file arrived: 2 minutes 26 seconds, 16,366 AI credits, about 2 euro cents of credits.
The clips were recorded on two Pulsed Media test accounts: one stands in for your Linux machine (shown as you@laptop) and the other for the Storage Box (shown as boxuser@storagebox). They were recorded one after the other, and long waits are shortened.
What stays private
rclone's crypt remote encrypts on your machine before anything is uploaded. File contents are encrypted with NaCl SecretBox (the XSalsa20 cipher with a Poly1305 integrity check), and file and directory names are encrypted by default (rclone crypt documentation). The Storage Box receives the result and has no key for it.
The box can still see:
- File sizes. rclone does not encrypt file length. Every file gets a 32-byte header and 16 bytes for each chunk of up to 64 KiB, so a stored size gives the real size away. In the test run a 19-byte file is 67 bytes on the box and a 300,000-byte photo is 300,112 bytes.
- Modification times. The documentation lists them as not encrypted either: rclone uses them for syncing.
- How many files there are and how the folders nest. Names are scrambled, but standard mode keeps the folder structure, and the same file name always becomes the same scrambled name.
- When you connect and from which address. That is what any server sees of an SFTP login.
The passphrase is the key, and it lives in a file on your machine. rclone keeps it in rclone.conf only lightly obscured: the documentation says that protects it from cursory inspection and is not secure unless the config file itself is encrypted. rclone tries to keep the file readable by you alone (mode 600 on the test account). Whoever can read that file can decrypt your copies, so the box stays unable to read them only while the file stays on your machine. Run rclone on a seedbox instead and the passphrase sits on a Pulsed Media server; Client-Side Encryption for Your Seedbox or Storage Box has that warning and the other ways to encrypt before upload.
rclone's documentation suggests a config password where you cannot keep the file safe (rclone config, option s). Pikkumies' rclone tool stops when it finds an encrypted config and never asks for the password, so with a config password you run the rclone commands yourself in your own terminal. Keep the passphrase in a password manager as well: with it you can re-create the remote on another machine and read the copies, and without it nobody can.
Pikkumies sees what you ask and what rclone prints back. Your request, the commands and their output, including file names, go through Pulsed Media's AI credit service to the model that answers; the restic page explains what that means. The rclone tool never reads or prints the rclone config, and Pikkumies' rclone instructions tell it never to read or print it any other way (rclone config show, cat rclone.conf), so the passphrase is not meant to reach the conversation. Every copy shows the file names in its preview and its listing, so the names reach the model. If the names themselves are private, run rclone in your own terminal and leave Pikkumies out of that folder.
Before you start
- A Linux machine you control, with rclone.
sudo apt install rcloneworks, or use rclone.org/downloads. Debian's own package is older (1.60.1 on Debian 12): copies work with it, but Pikkumies' sync and move need rclone 1.66 or newer. The prompts in step 2 are those of rclone 1.69.1. - Pikkumies on that machine, and key login to the box. Steps 1 and 2 of Zero-Knowledge Backups with Pikkumies cover both.
- A Storage Box with its server name and username.
Step 1: Add the box as an rclone remote
Replace SERVERNAME and USERNAME with your own. The remote uses your SSH key, so no password is typed or stored, and known_hosts_file makes rclone check the box's host key against the one SSH recorded when you first connected. key_file takes a key without a passphrase; for a key with one, add it to ssh-agent and leave key_file out (rclone SFTP documentation):
export BOX_HOST=SERVERNAME.pulsedmedia.com export BOX_USER=USERNAME rclone config create storagebox sftp host=$BOX_HOST user=$BOX_USER key_file=~/.ssh/id_ed25519 known_hosts_file=~/.ssh/known_hosts
Step 2: Create the encrypted remote
You type the passphrase here, never Pikkumies. Run rclone config and answer the prompts like this:
| Prompt | Answer |
|---|---|
e/n/d/r/c/s/q> |
n (new remote)
|
name> |
secretbox
|
Storage> |
crypt
|
remote> |
storagebox:rclone-crypt
|
filename_encryption> |
Enter (standard) |
directory_name_encryption> |
Enter (true) |
y/g> |
y, then type your passphrase twice
|
y/g/n> (salt password) |
Enter (none) |
Edit advanced config? |
Enter (no) |
y/e/d> |
y, then q to quit
|
Pick a long passphrase of your own: rclone recommends one, and the typing is hidden. The salt password is the second prompt; rclone calls it optional but recommended, and it is effectively a second password you must remember, so the clip skips it. The path after the colon has no leading slash: on a Pulsed Media box it is relative to your home directory.

rclone config prompts. The passphrase is typed twice and never shows on screen. The test box's name and username are replaced on screen.Use the crypt remote for everything. rclone's documentation warns that anything written straight to storagebox:rclone-crypt is not encrypted, and anything read from it is the scrambled form.
Step 3: Ask Pikkumies for the copy
One sentence is the whole request:
pikkumies "Copy my Documents folder to my encrypted remote secretbox: and show me what is there afterwards. Keep it short."

rclone cryptcheck run from your side: 0 differences found, 3 matching files.What comes back:
- the files copied and their size, here 3 files and 300,035 bytes;
- a second
checkthat finds nothing left to copy. It compares sizes and modification times, so it shows that every file arrived, not that the contents match; - the listing of the folder, in plain names, because rclone decrypts them for you.
Pikkumies' copy adds files and never deletes. A file that is already on the box is left alone unless you ask for a replacement, and the replaced file is then gone. Sync and move delete, so Pikkumies first shows what they would change and runs them only with the number from that preview.
Check it yourself
Pikkumies has no content check for a crypt remote, and rclone's check cannot compare the checksums of encrypted files. rclone cryptcheck can. It uses the passphrase from your config, so you run it in your own terminal:
rclone cryptcheck ~/Documents secretbox:Documents
The last lines of the clip above show it: 0 differences found and 3 matching files.
What the Storage Box sees
On the box itself, the folder holds scrambled names, sizes that follow the rule above, and no readable text. A search for a line that is in one of the documents finds nothing:
ls rclone-crypt find rclone-crypt -type f -printf '%s %p\n' grep -r 'rent 2026' rclone-crypt || echo 'not found'

Getting files back
Run rclone yourself to restore one file into a new folder (this command was run on the test account):
rclone copy secretbox:Documents/taxes/2026.txt ~/restore-check/taxes
Pikkumies' copy can also go from a remote to a folder inside your home. It leaves files that already exist there as they are, so restore into an empty folder.
Troubleshooting
- directory not found when listing
secretbox:before the first copy: the folder does not exist on the box until something is copied into it. After a first copy it is there. If it persists, check the path in the remote: a path that starts with a slash (storagebox:/rclone-crypt) points at the root of the server and gives the same error. - Skipping undecryptable dir name: bad PKCS#7 padding and an empty listing: the passphrase (or the salt password) does not match the one the copies were made with. Names and contents only open with the same ones.
- failed to read private key file: the path in
key_fileis wrong. Point it at the private key that matches the public key you gave the box (step 1 of the restic page). - Pikkumies says the rclone config is encrypted and stops: that is by design, see the config password note above. Run rclone in your own terminal, or keep the config unencrypted.
- A copy that does not change after you edit a file: Pikkumies' copy does not overwrite. Ask for the replacement explicitly, knowing the old version on the box is then gone.
What a run costs
The test run above used 16,366 credits for 3 files; a larger folder takes longer and can use more. Active Pulsed Media services earn credits; how Storage Box payments earn them is on the restic page. See the Storage Box plans.
See also
- Zero-Knowledge Backups with Pikkumies: the same goal with restic, which keeps snapshots and deduplicates
- Client-Side Encryption for Your Seedbox or Storage Box: gpg, rclone crypt and encrypted folders
- Rclone: installing and using rclone with a seedbox
- Pikkumies on PMSS: what Pikkumies is and how it works in a seedbox account
- Storage Boxes: plans, protocols and backup tools