#312 Encrypt/omit backup source directories in backed up target config file

[user198379]

Areca usually stores a copy of the target config file in the backup repository. If the user choses to encrypt filenames, the config file undoes some of that security by revealing the paths of the source directories in unencrypted plain text.

Perhaps that part of the config file can be omitted when stored with the backup archive, or enrypted using the same credentials as the archive data.

I'm not sure how Areca uses those paths, so I don't know if either suggestion is practical.