rclone / rclone/rclone

Add "cryptdecode" function as a flag (--cryptdecode remote:) to copy/move/etc. commands?

Open
#7,804 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Go
Stars
59.8k
Forks
5.4k
Avg merge
2d 14h
Merged PRs (30d)
48

Description

The associated forum post URL from https://forum.rclone.org

https://forum.rclone.org/t/possibility-of-decrypting-the-log-entries-in-realtime/5154

What is your current rclone version (output from rclone version)?

rclone v1.66.0

  • os/version: darwin 13.6.6 (64 bit)
  • os/kernel: 22.6.0 (x86_64)
  • os/type: darwin
  • os/arch: amd64
  • go/version: go1.22.1
  • go/linking: dynamic
  • go/tags: cmount
What problem are you are trying to solve?

Be able to work with encrypted files in remotes and see what's going on in log files, etc.

How do you think rclone should be changed to solve that?

Add "--cryptdecode" as a flag to copy/move/etc. commands.

I.e: rclone copy remote1: remote2: -v --cryptdecode remote1-crypt:

How to use GitHub
  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing how the copy, move, and related commands define and share flags, then read the linked forum discussion about decrypting log entries in real time. Define how --cryptdecode remote: should affect those commands and verify the behavior with the example involving remote1-crypt:. Done means encrypted filenames or log entries can be handled as requested without changing normal command behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.