update 1.2.2.2 beta

web/messages/en/docs/backup-restore/destinations/pbs.json

@@ -52,7 +52,13 @@
     "heading": "Client-side encryption",
     "intro": "PBS client-side keyfile encryption encrypts chunks on the source host before upload. ProxMenux enables the feature with one added constraint: a recovery passphrase is mandatory when encryption is enabled. The passphrase does not protect the local keyfile; it protects the escrow copy of the keyfile that ProxMenux uploads to PBS for disaster recovery.",
     "keyfileTitle": "Keyfile",
-    "keyfileBody": "On first use, <code>proxmox-backup-client key create --kdf none</code> generates the keyfile at <code>/usr/local/share/proxmenux/pbs-key.conf</code> (<code>chmod 600</code>). Subsequent backups reuse it after a single confirmation dialog. If key creation fails, the backup is cancelled and the tool's error output is shown in a dialog.",
+    "keyfileBody": "Both the CLI wizard and the Monitor Web modal expose the encryption setup as a three-way choice: <em>generate a new keyfile</em>, <em>import an existing one</em>, or <em>skip</em>. <em>Generate</em> runs <code>proxmox-backup-client key create --kdf none</code> and writes the keyfile at <code>/usr/local/share/proxmenux/pbs-key.conf</code> (<code>chmod 600</code>). <em>Import</em> takes a keyfile the operator already has (typically the one used on other hosts) and installs it at the same path after validating it with <code>proxmox-backup-client key info</code>. Subsequent backups on the same host reuse whichever keyfile is installed after a single confirmation dialog. If any step fails, the backup is cancelled and the tool's error output is shown in a dialog.",
+    "modesTitle": "Per-host or shared keyfile",
+    "modesIntro": "Both operating models are supported and neither is enforced — the choice belongs to the operator based on how their fleet is organised.",
+    "modesPerHostTitle": "Per-host keyfile (default)",
+    "modesPerHostBody": "Each host generates its own keyfile the first time it enables PBS encryption. Isolation is maximum: compromising the keyfile of one host does not expose the backups of any other. Each host has its own paired recovery blob on PBS, restorable with the recovery passphrase of that host. Recommended for production fleets and for environments where hosts have different owners or compliance boundaries.",
+    "modesSharedTitle": "Shared keyfile (import on every host)",
+    "modesSharedBody": "One master keyfile generated once and installed on every host via the <em>Import</em> option. Management is simpler: a single secret to safeguard, a single recovery blob works for every host, and any host can decrypt the archives of any other (useful for consolidation, cross-host restore drills, or centralised backup verification). The trade-off is that a leak of the shared keyfile exposes every host at once. Recommended for homelabs and for fleets where all hosts have the same owner and trust boundary.",
     "recoveryTitle": "Recovery passphrase and escrow blob",
     "recoveryBody": "After the keyfile is created, ProxMenux prompts twice for a recovery passphrase (with match validation) and runs <code>openssl</code> to produce <code>pbs-key.recovery.enc</code> — the keyfile encrypted with the passphrase. A copy is written to <code>/root/pbs-key.recovery-HOSTNAME-YYYYMMDD.enc</code> for offsite storage. Cancelling the passphrase dialog wipes the freshly-created keyfile.",
     "blobUploadTitle": "Paired backup group on PBS",