Backup signing in Plesk


2016-11-16 13:05:41 UTC


2017-08-16 17:18:08 UTC


Was this article helpful?

Have more questions?

Submit a request

Backup signing in Plesk

Applicable to:

  • Plesk for Linux
  • Plesk 11.x for Windows
  • Plesk 11.x for Linux
  • Plesk 12.0 for Linux


Parallels Plesk Panel Micro-Update #3 for Plesk 11.5 introduced a new security measure: signing of backup files. This article addresses questions that may arise due to this feature and explains the customer impact.

What are backup signatures for?

Backups are signed with a server-specific key in order to ensure that the backup is made on the same server and has not been modified. This security measure protects against attempts to restore forged backups in order to increase limits or gain permissions.

When are backups signed?

Backups are signed in the following cases:

  • The backup is created in the FTP server repository.
  • The backup is downloaded from the Parallels Plesk Panel interface.
  • The backup is created using the pleskbackup command-line utility, even if the argument for -output-file is a local file.

Backups created on the server and stored in the local repository are not signed.

When is a backup signature verified?

A backup signature is verified in the following cases:

  • The backup is uploaded through the control panel.
  • The backup is restored from FTP.
  • The backup is copied from the Personal FTP repository to the Server Repository.
  • The backup is restored from a single file using the pleskrestore command-line utility.

What happens when the server cannot verify a backup signature?

Uploading or restoring of backups with absent or incorrect signatures is not allowed for non-administrator accounts. The Plesk administrator is asked for an additional confirmation when an unsigned or unverified backup is uploaded or restored.

How will the introduction of backup signature checks impact my customers?

  1. All backups uploaded to FTP or downloaded through the control panel before 11.5 MU#3 was installed will be processed as unsigned. This means the following:

  2. Non-administrators cannot restore such backups from Personal FTP Repository.

  3. Non-administrators cannot upload backups downloaded before installing 11.5 MU#3 to Server Repository.
  4. Non-administrators cannot restore their parts of full server backups that are not signed or have incorrect signatures (such backups may be uploaded by the administrator).

  5. The administrator has to confirm the uploading or restoring of unsigned backups or backups with incorrect signatures in the control panel interface and in the command-line utilities:

  6. pleskrestore will not start to restore a backup with an incorrect signature unless you add the -ignore-sign option.

  7. The I want to restore this backup despite the fact that it is modified check-box should be selected on the Backup Details and Upload Backup File from Local Computer to Server Repository pages in an Administrator control panel session.

  8. If a backup on Remote FTP Repository has an incorrect signature, it cannot be moved to Server Repository by the Copy to Server Repository button, not even by the administrator. The product development team is working on a permanent solution for this. The current workaround is to download the backup from the FTP server and then upload it through the Plesk interface to Server Repository .

I don't need it! How can I disable this feature?

Signature checking may be turned off through the /usr/local/psa/admin/conf/panel.ini configuration file ( %plesk\_dir% \\admin\\conf\\panel.ini on Windows):

allowRestoreModifiedDumps = on

In this case, the signature will be checked, but will not block any operation.

Have more questions? Submit a request
Please sign in to leave a comment.