From: Jean-Laurent Ivars <jl.ivars@ipgenius.fr>
To: pve-user@pve.proxmox.com
Subject: [PVE-User] Security Proxmox Backup Server
Date: Sun, 27 Mar 2022 00:31:09 +0700 [thread overview]
Message-ID: <A610A458-CC3C-432D-9EAC-984858894177@ipgenius.fr> (raw)
Hello everyone,
To give you a bit of context I’m pretty comfortable with PVE that I use for years and enjoy so much for everything it can do, it’s simplicity while being so full of possibilities and it’s stability.
Until today I never had installed a PBS and now I’ve done it but I haven’t spent so much time on the configuration nor on learning how to use it yet, even though it seems very promising !
Having searched the perfect solution for backup my PVE clusters and VMs for years it seems it’s finally getting there and so now Proxmox is (finally) a real solution that miss absolutely nothing to be production ready, though I have a question : I’ve seen in the doc many times that it’s not a problem if the PBS is not fully trusted because it’s possible to activate encryption on the client side but what if it’s the client, VM or the PVE cluster that becomes untrustworthy ? Let’s say my cluster get hacked !
Is there a way it compromises the backups ?
Sorry if my question seems obvious but it would save me a lot of time because if that wasn’t the case (which wouldn’t make sense so I doubt it) it would be a no go for me, so I wouldn’t lose my time learning more about it, even though it seems a great deal with all these options and fonctions !
Thank you for having took the time to read me and don’t hesitate to send me some links ;)
Thank you so much in advance !
Best Regards,
Jeanlau
next reply other threads:[~2022-03-26 17:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-26 17:31 Jean-Laurent Ivars [this message]
2022-03-26 18:58 Dietmar Maurer
2022-03-26 19:24 ` Jean-Laurent Ivars
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A610A458-CC3C-432D-9EAC-984858894177@ipgenius.fr \
--to=jl.ivars@ipgenius.fr \
--cc=pve-user@pve.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox