gilbertchen
Option to store Snapshot ID Encrypted or Hashed
The snapshot id is an id used to distinguish different repositories connected to the same storage. Each repository must have a unique snapshot id. A snapshot id must contain only characters valid in Linux and Windows paths (alphabet, digits, underscore, dash, etc), but cannot include /, , or @.
I appreciate the flexibility of being able to name a Snapshot ID whatever you like, but I'm not entirely sure of the best way to utilize them. I have adopted them as a way to separate out my Devices and their Root Folders intended for Backing Up:
- MyXPS15.Documents
- MyXPS15.Desktop
- MyXPS15.Photos
- GamingPC.Desktop
- ...
This seems like as good a way as any to use it, but its a little frustrating that the folders it creates are in plaintext. I'd rather no identifying information was exposed. Given that everything else is stored encrypted or hashed, it would be nice if these SnapshotID folders were too. Or perhaps just as a Random Hash with a reference in the Config to resolve to a particular SnapshotID.
I get that I could just name them something obscure or random myself, but that makes it hard to know/remember what to target when recovering or backing up.
One benefit of doing this, would be it can allow the usage of characters not normally allowed in folders. So that SnapshotIDs could include things like / or : . See this issue.
It is not hard to implement this option, but it will require changes in a lot of places. I'm marking this as an enhancement for now, but will only consider it if more users come out to request it.
