We have regular backups generated on the WHM server and these are sent as .tar.gz files to an external depository.
There is a lot of talk on the forums about encrypting the transportation connection, but not much about encrypting the actual .tar.gz files themselves, This means that when the backup file is delivered to the other end, anyone with access to that account (Amazon / Google Drive / etc. ) have unhindered access to the backup of the entire account details and email.
I would be looking for some sort of locking mechanism on the .tar.gz generated files (perhaps using the password that is set for the account on WHM) or even better using a GPG encryptor such as Kleopatra. This would mean that anyone that has access to the depository account (Amazon / Google Drive / etc. ) does not automatically have access to the entire file/email/SQL readout of any backed up account.
I have had a look at this and can't see anything, ANYTHING that looks to do this, are there any options here?
There is a lot of talk on the forums about encrypting the transportation connection, but not much about encrypting the actual .tar.gz files themselves, This means that when the backup file is delivered to the other end, anyone with access to that account (Amazon / Google Drive / etc. ) have unhindered access to the backup of the entire account details and email.
I would be looking for some sort of locking mechanism on the .tar.gz generated files (perhaps using the password that is set for the account on WHM) or even better using a GPG encryptor such as Kleopatra. This would mean that anyone that has access to the depository account (Amazon / Google Drive / etc. ) does not automatically have access to the entire file/email/SQL readout of any backed up account.
I have had a look at this and can't see anything, ANYTHING that looks to do this, are there any options here?
Last edited by a moderator: