Esta es una versión anterior. La versión actual es 2.2.0. cv4pve-node-protect 2.2.0 · Fecha de publicación:
Archivos de instalación 2.0.0
| Arquitectura | Tipo | Ámbito | Tamaño del archivo | Descargar | SHA256 |
|---|---|---|---|---|---|
| 64 bits | ZIP → Portable | — | — | github.com | VirusTotal |
| ARM64 | ZIP → Portable | — | — | github.com | VirusTotal |
| 32 bits | ZIP → Portable | — | — | github.com | VirusTotal |
El enlace y el SHA256 proceden del manifiesto comunitario del Administrador de paquetes de Windows. Conviene comparar el hash del archivo descargado antes de ejecutarlo.
Notas de la versión
Added
- SSH private key authentication (--private-key-file, --passphrase) — log in with a private key instead of a password
- Read password from file (--password=file:/path) — keep the password out of shell history and process list
- Custom SSH port per host (--host=pve1:2222,pve2:2222)
Changed
- --paths and --directory-work are now required when running backup
- SSH port in --host=host:port is now actually honored (previously always used port 22)
- Backup retention only deletes timestamped backup folders — other folders in the work directory are left alone
- Updated to run on .NET 10 (the library still works on .NET 8, 9 and 10)
Removed
- upload command — it only copied the archive to the node without restoring anything. Manual restore via scp + tar is documented in the README.
- --dry-run option — it had no effect
Fixed
- Clear error when using --private-key-file without --username
- Temporary files on the node are always cleaned up, even if the backup fails halfway through
- Paths containing spaces or special characters are now handled safely
Security
- Temporary backup archives on the node now use restricted permissions and unpredictable names — other users on the same node can no longer read the cluster configuration while a backup is in progresshttps://github.com/Corsinvest/cv4pve-node-protect/releases/tag/v2.0.0
