public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] backup-exclude: Add suricata ruleset-sources to backup exclude file
Date: Wed, 15 Jan 2025 11:42:39 +0000	[thread overview]
Message-ID: <610F4E4D-CC79-4E74-89F5-6BA3EC75AF2F@ipfire.org> (raw)
In-Reply-To: <20250113122442.55641-1-adolf.belka@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]

Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>

> On 13 Jan 2025, at 12:24, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> - This will ensure that an old version will no longer be restored back onto a users
>   system.
> - The suricata ruleset-sources file should also be shipped in the CU that this will be
>   applied to make sure that all usders have the correct version installed, in case they
>   have done a restore from an old backup after doing a fresh install.
> - Tested on my vm testbed system and after making the change, the ruleset-sources file
>   is no longer added to the backup set but also it is excluded from the restore if it
>   is included in an old backup.
> 
> Tested-by: Adolf Belka <adolf.belka(a)ipfire.org>
> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
> ---
> config/backup/exclude | 1 +
> 1 file changed, 1 insertion(+)
> 
> diff --git a/config/backup/exclude b/config/backup/exclude
> index 0131a87fd..4dc1607a2 100644
> --- a/config/backup/exclude
> +++ b/config/backup/exclude
> @@ -7,4 +7,5 @@ var/ipfire/ovpn/openssl/*
> var/ipfire/proxy/calamaris/bin/*
> var/ipfire/qos/bin/qos.pl
> var/ipfire/suricata/oinkmaster.conf
> +var/ipfire/suricata/ruleset-sources
> var/ipfire/urlfilter/blacklists/*/*.db
> -- 
> 2.47.1
> 


      reply	other threads:[~2025-01-15 11:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-13 12:24 Adolf Belka
2025-01-15 11:42 ` Michael Tremer [this message]

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=610F4E4D-CC79-4E74-89F5-6BA3EC75AF2F@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /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