geek-merlin
geek-merlin
As of this proposal, i studied your comments in #172 and want to find a way to solve that. If you bear with me, maybe we can come up with...
Or, let me elaborate the process, maybe this helps. (As i understand it,) GC as described in #132 maintains 2 directories with magic names, and in #172 you said if...
Sorry for being off so long. This issue is still important to me, but "the house was on fire"... Thanks a lot @dpc to take all the time and explain...
That said, i still have the hope that we **can** find a GC strategy that works for all possible scenarios. Just to get everyone onto the same boat: @dpc, we...
If i get it right, we need the naming scheme for backups (correct me if one of the assumptions is wrong): - rdedup does a key-value store for names -...
> I'm open for having such thing integrated directly, but why does it have to use a naming scheme? The creation date etc. could be stored in the name file...
I deem this very valuable.
> I guess it might be possible to name them after the hash of the cyphertext That would not disable the attack. But interesting idea.
How difficult would an optional pubkey passphrase be?
I'm interested in this too. My usecase is to have a local repo that is rclone'd to cloud storage. The local and the cloud repo will have different prune/gc strategies...