From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Noel Ullreich <n.ullreich@proxmox.com>
Cc: Noel Ullreich <nullreich@eloa.proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup 4/5] docs: main features ransomware
Date: Thu, 24 Nov 2022 10:35:34 +0100 [thread overview]
Message-ID: <2fe7ffad-2811-7339-0b98-19d2c42b8e71@proxmox.com> (raw)
In-Reply-To: <20221123174810.2703466-5-n.ullreich@proxmox.com>
Am 23/11/2022 um 18:48 schrieb Noel Ullreich:
> From: Noel Ullreich <nullreich@eloa.proxmox.com>
>
> added ransomware protection as main feature of pbs
>
I'd squash this into the next patch and directly link to the new section.
> Signed-off-by: Noel Ullreich <n.ullreich@proxmox.com>
> ---
> docs/introduction.rst | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/docs/introduction.rst b/docs/introduction.rst
> index 2f392157..f1dec018 100644
> --- a/docs/introduction.rst
> +++ b/docs/introduction.rst
> @@ -76,6 +76,9 @@ Main Features
> provides extensive support for backing up to tape and managing tape
> libraries.
>
> +:Ransomware protection: Proxmox Backup Server provides protection from ransomware attacks via checksums and
> + user access control as well as mitigation of ransomware attacks by restoring from tape backups and remote syncs.
"code" style wise: please avoid overly long lines, target 80cc text-width,
also extra white space after the colon.
content wise I'd drop starting with PBS here and avoid mentioning "ransomware attack"
as often as three times, e.g., something like:
:Ransomware protection: Protect your critical data from ransomware attacks with
Proxmox Backup Server's fine-grained access control, data integrity
verification, and off-site backup through remote sync and tape backup.
> +
> :Web interface: Manage the Proxmox Backup Server with the integrated, web-based
> user interface.
>
next prev parent reply other threads:[~2022-11-24 9:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 17:48 [pbs-devel] [PATCH proxmox-backup 0/5] added section on ransomware to docs Noel Ullreich
2022-11-23 17:48 ` [pbs-devel] [PATCH proxmox-backup 1/5] readme: fixed typo in readme Noel Ullreich
2022-11-24 9:09 ` Thomas Lamprecht
2022-11-23 17:48 ` [pbs-devel] [PATCH proxmox-backup 2/5] docs: changed wording Noel Ullreich
2022-11-23 17:48 ` [pbs-devel] [PATCH proxmox-backup 3/5] docs: fixed capitalization Noel Ullreich
2022-11-23 17:48 ` [pbs-devel] [PATCH proxmox-backup 4/5] docs: main features ransomware Noel Ullreich
2022-11-24 9:35 ` Thomas Lamprecht [this message]
2022-11-23 17:48 ` [pbs-devel] [PATCH proxmox-backup 5/5] docs: added section on ransomware Noel Ullreich
2022-11-24 10:23 ` Thomas Lamprecht
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=2fe7ffad-2811-7339-0b98-19d2c42b8e71@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=n.ullreich@proxmox.com \
--cc=nullreich@eloa.proxmox.com \
--cc=pbs-devel@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.