To avoid code duplication, a dedicated component with the xtype
pmxFingerprintField was added to proxmox-widget-toolkit which we are
now also using here.
Signed-off-by: Hannes Duerr <h.duerr@proxmox.com>
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
two similar things to fix here:
* the 'crypt-allow-edit' field was not submitted, but it's value was
only ever set with a bind, so a reset always set it to it's
default 'false' value (disabling the radio buttons, even when
it was not visible)
* the initial value of the 'keep' variant of the radiofield was decided
only from 'isCreate' (via the 'checked' cbind), but should have been
decided by whether there was an encryption key or not.
both are fixed by setting the values in the 'setValue' method
explicitly
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
Reviewed-by: Fiona Ebner <f.ebner@proxmox.com>
Tested-by: Fiona Ebner <f.ebner@proxmox.com>
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
'typeof' cannot return 'undefined' only the string '"undefined"', newer
eslint versions detect that as error
to fix it, directly check it for undefined instead of using typeof
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
this gives users the chance to supply the port nr in the gui,
without having to add a extra new field to the panel.
using the same implementation as in RemoteEdit.js in PBS.
Signed-off-by: Lorenz Stechauner <l.stechauner@proxmox.com>
it is not that short in other languages, e.g. German
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
Normally it's better to configure pruning (backup retention) on the
backup server only, as then multiple client settings may not
interfere with each other due to outdated or to strict prune
settings (remember, the strictest prune setting always wins).
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
note that the key is really important, add our recommended backup
strategy (copy to PW manager, save onto secured USB drive, print
paperkey and secure it) with the respective buttons to do so.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
a bit more complicated than wished, but if we want to have at least a
bsaic OK user experience we need to give good feedback that the key
will be deleted.
We definitively want to extend this, allow uploading their own,
export if root@pam, only move not delete on "removal", for safety.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
