feat: ZIP encryption option in profile settings #121

New Issue

2026-06-23T16:04:44Z

jmiller commented

2026-06-23 16:04:44 +00:00

Summary

The encryption_password field already exists in the profile form and BackupEngine applies AES-256 encryption when set. Verify the field is visible and working in the current profile UI. If not visible, ensure it shows in the Archive Settings tab.

Note: AES-256 ZIP encryption requires PHP compiled with libzip 1.2.0+ and ZipArchive::EM_AES_256 constant.

Check

Is the encryption_password field visible in the profile form?
Does setting it actually encrypt the archive?
Is there a strength indicator like the webcron field?

## Summary The encryption_password field already exists in the profile form and BackupEngine applies AES-256 encryption when set. Verify the field is visible and working in the current profile UI. If not visible, ensure it shows in the Archive Settings tab. Note: AES-256 ZIP encryption requires PHP compiled with libzip 1.2.0+ and `ZipArchive::EM_AES_256` constant. ## Check - Is the encryption_password field visible in the profile form? - Does setting it actually encrypt the archive? - Is there a strength indicator like the webcron field?

jmiller added the component: admin label 2026-06-23 16:04:44 +00:00

jmiller commented

2026-06-23 17:58:47 +00:00

Verified — the encryption_password field is already present and visible in profile.xml (Archive Settings fieldset, lines 96-101). It renders as a standard password input with no showon condition, so it always appears in the Archive Settings tab.

The encryption flow in BackupEngine::run() reads the field at line 228 and calls encryptArchive() which applies WinZip-compatible AES-256 encryption via ZipArchive::setEncryptionName() on every file in the archive. The method also validates that ZipArchive::EM_AES_256 is available (PHP 7.2+ with libzip 1.2.0+) and throws a clear error if not.

No changes needed — closing as already implemented.

Verified — the `encryption_password` field is already present and visible in `profile.xml` (Archive Settings fieldset, lines 96-101). It renders as a standard password input with no `showon` condition, so it always appears in the Archive Settings tab. The encryption flow in `BackupEngine::run()` reads the field at line 228 and calls `encryptArchive()` which applies WinZip-compatible AES-256 encryption via `ZipArchive::setEncryptionName()` on every file in the archive. The method also validates that `ZipArchive::EM_AES_256` is available (PHP 7.2+ with libzip 1.2.0+) and throws a clear error if not. No changes needed — closing as already implemented.

jmiller closed this issue

2026-06-23 17:58:56 +00:00

jmiller referenced this issue from a commit

2026-06-23 18:05:50 +00:00

feat: purge, CPanel module, 7z format, SFTP browser (#119, #105, #122, #98)

jmiller referenced this issue

2026-06-23 18:05:55 +00:00

feat: Purge, CPanel module, 7z format, SFTP browser (#119, #105, #122, #98) #135

Sign in to join this conversation.