Buddy Backup and Encryption

[TheGlitch]

So I noticed that HexOS requires encryption at the folder-creation stage for future offsite backups. Since Buddy Backup isn't out yet, how will the migration path look for users who have already populated large unencrypted datasets?

Specifically:

1. Will there be a built-in 'Migrate to Encrypted' tool to move data into a new encrypted dataset for Buddy Backup?

2. Will Buddy Backup support 'Replication-level encryption' (encrypting the stream during transit/at rest on the destination) without requiring the source folder on my local NAS to be encrypted?

3. What about application data folders that are already not encrypted, how would those be handled?

[PsychoWards]

As much as I like the idea of encrypted datasets (i'm using them myself), I fear that it will cause a not insignificant amount of headaches and data loss.

Seeing how many users currently are just reinstalling Hexos if something is not working as they expect, currently, they just nees to mount the pools again and no harm no foul.

But with encrypted datasets, where they didn't save the keys or have the keys saved on the encrypted dataset themselves it's bye bye data. 

So if we go done the path of encrypted datasets, we need to have a way to easily manage the decryption keys. Maybe there will be an option to store them on the Hexos Server and use them from there if anything ever goes wrong with a server. If not, a lot of people are not going to remember where they put those keys X years ago, which are now standing between them and their data.

Don't get me wrong, I think those are definitely valid points, but such a crucial part requires a basically fool proof setup to not cause any harm. 🙂